Optical accessory for attachment to mobile device

ABSTRACT

An attachment for use with a mobile device with an imaging device or with a case for the mobile device can include one or more of an attachment base and an attachment body. The attachment base can be configured to be secured to at least one of the mobile device and the case. The attachment body can include at least one optical device for use with the imaging device and can be configured to be secured to the attachment base. The attachment base can removably secure the attachment body to the mobile device or the case when the attachment body is secured to the attachment base.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of co-pending U.S. patentapplication Ser. No. 15/092,028, titled “Optical Accessory forAttachment to Mobile Device” and filed on Apr. 6, 2016, which is acontinuation-in-part of co-pending U.S. patent application Ser. No.14/682,062, titled “System for Capturing a Coded Image” and filed onApr. 8, 2015 and a continuation-in-part of co-pending U.S. patentapplication Ser. No. 14/682,072, titled “Aimer Accessory for Capturing aCoded Image” and filed on Apr. 8, 2015, all of which are incorporatedherein by reference.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not applicable.

FIELD OF THE INVENTION

The present invention relates to devices for optically acquiring data,and in particular, to optical barcode scanning devices.

BACKGROUND OF THE INVENTION

Handheld image and barcode scanning devices are well known and used in awide range of enterprise applications. Barcode scanners are regularlyused in connection with checkout stations at supermarkets and otherretail establishments for reading barcodes on consumer goods. They arealso useful in inventory collection and control for warehousing,shipping and storage of products.

Mobile electronic devices, such as smartphones and tablet computers, arewell known and leveraged in a wide range of corporate and personalapplications. Such devices, executing specialized software, arefrequently being utilized to scan and decode barcodes on products,promotions, and coupons. The specialized software, or app, is typicallydownloaded to the device but may be preloaded. The app configures thesmartphone or mobile device to use the built-in camera in the smartphoneor mobile device to scan barcodes, such as those found on products or inmagazines, stores, websites, and billboards.

Today's enterprise and personal workplace is changing. Technology isbecoming more integrated with daily processes and procedures. In amobile workplace, the mobile electronic device may provide a more costeffective and flexible alternative to traditional, dedicated andpurpose-built handheld scanning devices.

However, scanning a barcode with a smartphone or other mobile electronicdevice can be cumbersome. To scan a barcode, the user is typicallyrequired to view the barcode through the display screen of the device inorder to aim and focus the camera lens before the barcode can besuccessfully decoded. If the device's camera is not properly aimed andfocused, it may be difficult or impossible to read the barcode, or maytake an excessive amount of time to capture, detect, and decode thebarcode from an image. As a result, the scanning of barcodes using amobile electronic device is inefficient whenever there is a need forconvenient, rapid, or high volume barcode detection and decoding.Improving the efficiency and ease-of-use of barcode scanning, using thebuilt-in camera along with enhanced decoding software, is desirable.

Thus, methods and devices are needed to improve the efficiency andease-of-use of scanning a barcode using a mobile device, such as asmartphone.

SUMMARY OF THE INVENTION

Technologies are described for optical devices, and in particular to asystem for scanning a barcode using a smartphone and other mobiledevices.

Some embodiments of the invention provide an attachment for use with amobile device and a case for the mobile device. The mobile device caninclude an imaging device and a mobile-device light source, and the casecan include a case optical opening that is optically aligned with one ormore of the imaging device and the mobile-device light source when thecase is secured to the mobile device. The attachment can include anattachment base and an attachment body. The attachment base can beconfigured to be secured to the case with the attachment base disposedat least partly within the case optical opening, and the attachment bodycan be configured to be removably secured to the attachment base. Theattachment body can include at least one optical device for use with theimaging device during image targeting and image acquisition. Theattachment base can removably secure the attachment body to the casewhen the attachment body is secured to the attachment base and theattachment base is secured to the case.

Some embodiments of the invention provide a system for communicatingwith a mobile device, where the mobile device includes an imaging deviceand a mobile-device light source. The system can include an attachmentwith a light detector, at least one attachment light source, and aprocessor. The light detector can be configured to receive opticalsignals from the mobile-device light source. The processor can beconfigured to, based upon the optical signals received at the lightdetector from mobile-device light source, at least one of activate theat least one attachment light source to direct light onto an externaltarget and configure at least one illumination parameter for theattachment. The processor can further be configured to activate the atleast one attachment light source to communicate with the mobile devicevia the imaging device.

Some embodiments of the invention provide a method of communicatinginformation between a mobile device and an attachment, where the mobiledevice includes an imaging device and a mobile-device light source, andthe attachment includes a light detector and at least one attachmentlight source. First optical signals can be received at the lightdetector. Based on the first optical signals, at least one of: the atleast one attachment light source can be activated for image acquisitionand targeting; and at least one illumination parameter for theattachment can be configured. The at least one attachment light sourcecan also be activated to provide second optical signals to the imagingdevice to transmit non-image information to the mobile device.

To the accomplishment of the foregoing and related ends, the invention,then, comprises the features hereinafter fully described. The followingdescription and the annexed drawings set forth in detail certainillustrative aspects of the invention. However, these aspects areindicative of but a few of the various ways in which the principles ofthe invention can be employed. Other aspects, advantages and novelfeatures of the invention will become apparent from the followingdetailed description of the invention when considered in conjunctionwith the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The features and advantages of the invention are apparent from thefollowing description taken in conjunction with the accompanyingdrawings in which:

FIGS. 1A and 1B, collectively referred to herein as FIG. 1, show adiagram depicting aspects of a mobile device such as a smartphone;

FIG. 2 is an illustrative topology for components of the mobile deviceof FIG. 1;

FIGS. 3A and 3B are collectively referred to herein as FIG. 3. FIG. 3Ais a perspective diagram depicting an illustrative embodiment of anaimer accessory coupled to the mobile device of FIG. 1, and FIG. 3B isan exploded view of the aimer accessory of FIG. 3A;

FIGS. 4A through 4E, collectively referred to herein as FIG. 4, aredepictions of embodiments of possible light patterns produced by themobile device and accessory depicted in FIG. 3;

FIGS. 5A through 5D are illustrations depicting light patterns generatedby the aimer accessory of FIG. 3 in relation to a barcode;

FIG. 6 depicts an illustrative method according to this disclosure forusing the aimer module of this disclosure;

FIG. 7 depicts an example of a PDF417 barcode useful for understandingthe method of FIG. 6;

FIG. 8 depicts an illustrative memory map of bar code symbologies usedin the method of FIG. 6;

FIG. 9 depicts an alternative embodiment of an aimer accessory;

FIG. 10 is an exploded view of the aimer accessory of FIG. 9;

FIG. 11 depicts yet another embodiment of an aimer accessory of thisdisclosure;

FIG. 12 depicts aspects of light patterns and relationships of themobile device and aimer accessory of FIG. 11 with a barcode;

FIGS. 13A through 13C, collectively referred to herein as FIG. 13, areperspective diagrams depicting aspects of the aimer accessory depictedin FIG. 11;

FIGS. 14A through 14C, collectively referred to herein as FIG. 14, areperspective diagrams depicting aspects of the aimer accessory depictedin FIG. 3;

FIGS. 15A through 15C, collectively referred to herein as FIG. 15, areperspective diagrams depicting aspects of another embodiment of theaimer accessory;

FIGS. 16A through 16C, collectively referred to herein as FIG. 16, areperspective diagrams depicting aspects of the aimer accessory depictedin FIG. 9;

FIGS. 17A through 17C, collectively referred to herein as FIG. 17, areperspective diagrams depicting aspects of another embodiment of theaimer accessory;

FIGS. 18A through 18B, collectively referred to herein as FIG. 18, areperspective diagrams depicting aspects of another embodiment of theaimer accessory;

FIG. 19 depicts illustrative components of software useful for readingbarcodes with the aimer accessory;

FIGS. 20A, 20B, and 20C, collectively referred to herein as FIG. 20, areperspective drawings of alternative embodiments of this disclosureindicating possible shapes for the light source;

FIG. 21 are illustrative embodiments of light pipes or light-ray tracepaths that are taught by this disclosure;

FIG. 22 depicts an illustrative method according to this disclosure foradjusting the decoding position of the software decoder to align withthe shape and usage of the light pattern;

FIGS. 23 through 26 depict perspective drawings of an illustrative aimeraccessory according to this disclosure;

FIG. 27 depicts an illustrative method for retrofit of a mobile devicewith the aimer accessory of this disclosure;

FIG. 28 is a top, left, rear perspective view of an attachment assemblyfor an aimer accessory according to this disclosure;

FIG. 29 is an exploded, top, left, rear perspective view of theattachment assembly of FIG. 28;

FIG. 30 is an exploded, bottom, left, front perspective view of theattachment assembly of FIG. 28;

FIG. 31 is a perspective sectional view of the attachment assembly ofFIG. 28, taken along plane A-A of FIG. 28;

FIG. 32 is a perspective sectional view of the attachment assembly ofFIG. 28, taken along plane B-B of FIG. 28;

FIG. 33 is another perspective sectional view of the attachment assemblyof FIG. 28, taken along plan B-B of FIG. 28;

FIG. 34 is a front elevation view of an insert for the attachmentassembly of FIG. 28 and part of a case for a mobile device;

FIG. 35 is a front elevation view of the insert of FIG. 34 engaged withthe case of FIG. 34;

FIG. 36 is a rear elevation view of the insert of FIG. 34 engaged withthe case of FIG. 34, with a mobile device inserted into the case;

FIG. 37 is a top, left, rear perspective view of the attachment assemblyof FIG. 28 secured to the case of FIG. 34 for use with the mobile deviceof FIG. 36;

FIG. 38 is a top, left, rear perspective view of an attachment bodyaccording to this disclosure;

FIG. 39 is a top, right, front perspective view of the attachment bodyof FIG. 38;

FIG. 40 is a bottom, right, rear perspective view of an attachment baseaccording to this disclosure;

FIG. 41 is a bottom, right, front perspective view of the attachmentbase of FIG. 40;

FIG. 42 is a side sectional view of the attachment body of FIG. 38removably secured to the attachment base of FIG. 40, taken along planeC-C of FIG. 38 and plane D-D of FIG. 39, respectively;

FIG. 43 is a top, left, rear perspective view of the attachment body ofFIG. 38 engaged with the attachment base of FIG. 40, with the attachmentbase engaged for use with a mobile device;

FIG. 44A is a schematic view of an optical device for projecting apattern onto a target according to this disclosure;

FIG. 44B is a schematic view of a mask for the optical device of FIG.44A;

FIG. 45 is a schematic view of another optical device for projecting apattern onto a target according to this disclosure;

FIG. 46 is a schematic view of still another optical device forprojecting a pattern onto a target according to this disclosure;

FIG. 47 is a schematic view of yet another optical device for projectinga pattern onto a target according to this disclosure;

FIG. 48 is a schematic view of a further optical device for projecting apattern onto a target according to this disclosure;

FIG. 48B is a schematic view of a reflecting surface for the opticaldevice of FIG. 48A;

FIG. 49 is a schematic view of still a further optical device forprojecting a pattern onto a target according to this disclosure;

FIG. 50 is a top, rear perspective view of an attachment according tothis disclosure, as secured to a case for a mobile device;

FIGS. 51A and 51B are top and bottom perspective views of an attachmentbase for the attachment of FIG. 50;

FIGS. 52A and 52B are top, rear perspective and rear elevation views,respectively, of the attachment base of FIGS. 51A and 51B installed withthe case of FIG. 50;

FIGS. 53A and 53B are top and bottom perspective views, respectively, ofa base plate for the attachment of FIG. 50;

FIG. 54 is a perspective view of a battery door configured to be securedto the base plate of FIGS. 53A and 53B;

FIG. 55 is a rear elevation view of a method of attaching the attachmentof FIG. 50 to the case of FIG. 50;

FIGS. 56 and 57 are perspective and cross-sectional views, respectively,of the base plate and battery door of FIGS. 53A through 54 secured to ashell of the attachment of FIG. 50;

FIG. 58 is an exploded perspective view illustrating certain internalcomponents of the attachment of FIG. 50;

FIG. 59 is a cross-sectional perspective view of the attachment, thecase, and the mobile device of FIG. 50;

FIG. 60A is a cross-sectional perspective view of part of the attachmentof FIG. 50, illustrating configuration options for a light source of theattachment;

FIGS. 60B through 60D are front perspective views illustratingillumination patterns resulting from the configuration options of FIG.60A;

FIG. 61 is a schematic view of a control architecture for the attachmentof FIG. 50;

FIG. 62 is a top, rear perspective view of another attachment accordingto this disclosure, as secured to another case for another mobiledevice;

FIGS. 63A and 63B are bottom and top exploded perspective views,respectively, of the attachment of FIG. 62;

FIG. 64 is a cross-sectional perspective view of the attachment, thecase, and the mobile device of FIG. 62; and

FIG. 65 is a schematic view of a communication and control methodaccording to this disclosure.

DETAILED DESCRIPTION OF THE INVENTION

In the following detailed description, reference is made to theaccompanying drawings that form a part hereof. In the drawings, similarsymbols typically identify similar components, unless context dictatesotherwise. The illustrative embodiments described in the detaileddescription, drawings, and claims are not meant to be limiting. Otherembodiments may be utilized, and other changes may be made, withoutdeparting from the spirit or scope of the subject matter presentedherein. It will be readily understood that the aspects of the presentdisclosure, as generally described herein, and illustrated in theFigures, can be arranged, substituted, combined, separated, and designedin a wide variety of different configurations, all of which areexplicitly contemplated herein.

Disclosed herein are methods and apparatus that permit users of mobiledevices, such as a smartphone, to perform “blind and targeted scanning”of barcodes and other information bearing symbols. Generally, themethods and apparatus include an aimer module that collimates diffuselight from a lamp (LED or flash mechanism) on a mobile device for use incapturing a barcode image. The aimer module may also be integrated intoa given mobile device or a protective case. Alternatively, the aimermodule may be configured as an attachment for retrofit of a mobiledevice. Operation of the mobile device may be complemented withadditional software to take advantage of the functionality of the aimermodule. In order to provide some background for the teachings herein,some context is first provided.

Referring now to FIG. 1, there is shown aspects of an illustrativemobile device 10. In this example, the mobile device 10 is a“smartphone.” Alternatively, the mobile device may be a tablet, anelectronic pad, a laptop computer, or other mobile device. Salientaspects of the mobile device 10 include a home button 6, an on/offswitch 3, a display 5, a camera 7, and a lamp 9. Generally, theforegoing components are conventional and provide functionality that iswell known in the art. The mobile device 10 may be referred to herein as“smartphone 10” and by other similar terms. Illustrative smartphonesinclude the IPHONE from Apple Corp. of Cupertino, Calif., devicesoperating on the ANDROID platform of Google Corp. of Mountain View,Calif., as well as devices operating in the WINDOWS environment providedby Microsoft Corp. of Redmond, Wash.

For purposes of convention and to aid in the discussion herein, terms oforientation are provided with regard to the figures. For example, FIG.1A depicts the front of the mobile device 10. FIG. 1B depicts the backof the mobile device 10. The terms of orientation are with reference toorientation during operation of the mobile device 10. Generally,orientation of other components, such as the aimer module introducedherein, are with reference to orientation of the mobile device 10. Forexample, it is conceivable the aimer module mentioned herein could beadapted for usage on the front facing camera of the mobile device.However, again, this is not limiting of the teachings herein.

Referring now to FIG. 2, an illustrative topology 20 of the mobiledevice 10 is provided. The illustrative topology 20 depicts some of thecomponents implemented in the mobile device 10. Included in theillustrative topology 20 is at least one central processing unit (CPU)26. The central processing unit (CPU) 26 is connected to or incommunication with other components through system bus 25. Illustrativeother components include a power supply 27, memory 21, software 22, usercontrols 8, a display 5, a camera 7 (can be front or rear facing onmobile device 10), a lamp 9, and a communication interface 23.

The CPU 26 may be an ARM or other processor. The power supply 27 may befrom a battery or a source of direct current (DC), such as a transformercoupled to a conventional alternating current (AC) outlet. User controls8 may be a home button 6 and an on/off switch 3 shown in FIG. 1. Display5 may include at least one of LCD, LED, OLED, AMOLED, IPS and othertechnologies. Lamp 9 may be a light emitting diode (LED).

The communication interface 23 may include a wired interface and/or awireless interface. The wireless interface may include a wirelessservice processor. Illustrative wireless interfaces may make use of aprotocol such as cellular, Bluetooth, Wi-Fi, near field technology(NFC), ZigBee, or other technology. Communication services provided overthe wireless communication interface may include Wi-Fi, Bluetooth,Ethernet, DSL, LTE, PCS, 2G, 3G, 4G, LAN, CDMA, TDMA, GSM, WDM and WLAN.The communication interface 23 may include an auditory channel. That is,the communication interface 23 may include a microphone for receivingvoice commands, and may further include a speaker. In some embodiments,the speaker may provide an auditory signal when a barcode has been read.The communication interface 23 may further include a status light orother such visual indicators.

The communication interface 23 provides for, among other things, voicecommunications as well as data communications. The data communicationsmay be used to provide for communication of software and data (such asat least one image; results of analyses, and other such types of data).Communication through the communication interface 23 may bebi-directional or in a single direction.

The mobile device 10 may include additional components such as sensors.Illustrative sensors may include an accelerometer that provides fororientation information and a GPS sensor that provides for locationinformation. The mobile device may also include peripheral interface andcommunication ports.

As discussed herein, the term “software” 22 generally refers tomachine-executable instructions that provide for the implementation ofthe methods of this disclosure that are explained below. Themachine-executable instructions may be stored on non-transitorymachine-readable media such as memory 21. Illustrative methods that maybe implemented to actuate the mobile device hardware may includeinstructions for operation of the camera 7, the lamp 9, communicationsthrough the communication interface 23, and other aspects of thisdisclosure as discussed further below. In some of the illustrativeembodiments discussed herein, the software 22 provides for detecting anddecoding barcodes within an image. However, it should be noted that theterm “software” might describe sets of instructions to perform a greatvariety of functions.

The memory 21 may include multiple forms of memory. For example, thememory 21 may include non-volatile random access memory (NVRAM) and/orvolatile random access memory (RAM). Generally, the non-volatile randomaccess memory (NVRAM) is useful for storing software 22 as well as datagenerated by or needed for operation of the software 22 such as rules,configurations and similar data. The memory 21 may include read onlymemory (ROM). The read only memory (ROM) may be used to store firmwarethat provides instruction sets necessary for basic operation of thecomponents within the topology 20.

The camera 7 may include any appropriate sensor and at least one opticalelement such as a lens. Generally, the camera 7 may include thosecomponents as needed to record (also referred to as “capture”) images ofitems such as a barcode and further include photodetectors, amplifiers,transistors, and processing hardware and power management hardware. Thelamp 9 may include any appropriate source of illumination. Illustrativecomponents for the lamp 9 include at least one light emitting diode(LED).

Although the illustrative mobile device 10 disclosed is a smartphone,the mobile device 10 is not limited to this embodiment and may includeother devices. Accordingly, it is not required that the mobile device 10incorporate all of the components of FIG. 2, and other components may beincluded. In order to provide some further context for the teachingsherein, some terms used herein are now introduced.

As discussed herein, the term “barcode” generally refers to an opticalmachine-readable symbology that contains a representation of data.Generally, any given barcode is a representation of data that is relatedto the object to which it is attached. A barcode as discussed herein mayinclude data that is arranged in a one-dimensional (1D) array, atwo-dimensional (2D) array; and/or a 3D physical tag. Information may beconveyed in a given barcode according to arrangements of symbology, andmay further convey information in a plurality of wavelengths and/orcolors (i.e., varying groups of visible wavelengths).

Illustrative forms of one-dimensional (1D) barcodes include: Codabar;Code 25 (Interleaved); Code 25 (Non-interleaved); Code 11; Code 39; Code93; Code 128; CPC Binary; DUN 14; EAN 2; EAN 5; EAN-8, EAN-13; FacingIdentification Mark; GS1-128; GS1 DataBar; HIBC; Intelligent Mailbarcode; ITF-14; JAN; KarTrak ACI; Latent image barcode; MSI;Pharmacode; PLANET; Plessey; PostBar; POSTNET; RM4SCC/KIX; Telepen; andUPC., as well as others.

Illustrative forms of two-dimensional (2D) barcodes (also referred to asa “matrix code”) include: Aztec Code; Code 1; ColorCode; Color ConstructCode; CrontoSign; CyberCode; d-touch; DataGlyphs; Data Matrix; DatastripCode; digital paper; EZcode; Color; High Capacity Color Barcode;HueCode; InterCode; MaxiCode; MMCC; NexCode; Nintendo e-Reader; Dotcode;PDF417; QR code; ShotCode; SPARQCode; and others.

As discussed herein, a “light pipe” or “light tube” is a physicalstructure used for transporting of light for the purpose of illuminationand is an example of an optical waveguide. A light pipe generallyprovides the transport of light to another location, minimizing the lossof light. A light pipe may include highly transmissive material, and mayinclude reflective materials, collectors, reflectors, concentrators, atleast one lens, and other components as deemed appropriate. Anillustrative light pipe is an optical fiber. Light pipes, as discussedherein, may be formed of any suitable material. Illustrative materialsinclude acrylic plastic, silicon glass, and other such materials. Alight pipe may be hollow and open or closed to the external atmosphere.A light pipe can be configured to transmit only light of a particularcolor (or colors).

Generally, the following discussion provides an introduction to an aimermodule, methods for use of the aimer module, aspects of someillustrative embodiments of the aimer module, and some detail onsoftware that may be used in conjunction with the aimer module.

Broadly speaking, an aimer module for a mobile device and method of useis provided by this disclosure. The aimer module collimates diffuselight from a lamp on a mobile device for use in capturing a barcodeimage. The aimer module includes a means for receiving light from a lampof the mobile device, and generating a light pattern on the surfacecontaining a barcode. The receiving and generating means may include agrating or configuration of mirrors. Registration of the light patternand the barcode in a scan area enhances the ability of the specializedsoftware on the mobile device to read the barcode.

As used herein, the term “registration” means that a barcode and a lightpattern generated by the aimer module on the surface containing thebarcode are in the viewing angle of the camera. This viewing angle canchange depending on the lens and the smartphone. In one illustrativeexample, the camera may use a cone type lens. In this example, if thebarcode and the light pattern on the surface containing the barcode areboth in the cone of viewing, there would be a registration of the lightpattern and the barcode according to this disclosure. As explained inthis disclosure, once the barcode and the light pattern generated by theaimer module on the surface containing the barcode are in“registration,” the smartphone may capture the barcode image and decodethe barcode as explained below.

Broadly speaking, there are at least three types of registrationcontemplated by this disclosure. These three types of registrationcorrespond to three modes of operation of the aimer module contemplatedby this disclosure. These three modes of operation are blind modescanning, targeted mode scanning, and smartphone display mode scanning,otherwise referred to as display mode scanning. In addition, both blindmode scanning and targeted mode scanning may be used with or withoutdisplay mode of operation. Hence, this disclosure provides for at leastfive modes of operation. These modes of operation are depicted in theTable 1 and are explained in greater detail below.

TABLE 1 Modes of operation of Smartphone or Other Mobile Device withAimer Module Blind Targeted Display Mode Mode Mode ConfigurationOperation Operation Operation Blind Mode Blind Configuration ON - ModeDisplay Not Used Blind Blind Mode Blind Configuration ON- Mode DisplayUsed Targeted Targeted MODE Targeted Configuration ON - Mode Display NotUsed Blind Targeted MODE Targeted Configuration ON- Mode Display UsedTargeted Blind Mode AND Display Targeted Mode Mode Configurations OFF-Display Used

In blind mode of operation, the light pattern on the surface containingthe barcode can be anywhere in the cone of viewing. The user uses thelight pattern generated by the aimer module of this disclosure as apointer and points the light pattern at the surface containing thebarcode. There is no need for the user to look through the display ofthe smartphone when operating the scanning features of this disclosurein blind mode. So long as the user aims the light pattern at the surfacecontaining the barcode, such that the light pattern and barcode are bothwithin the cone of viewing, there is a registration of the light patternand the barcode in blind mode according to this disclosure. As indicatedin Table 1, the user may employ blind mode operation with or without theuse of the display. The most efficient manner of blind mode operationinvolves a blind mode blind operation without the use of the display. Inthis case, the user would simply look at and direct the light patterngenerated by this disclosure at or around the barcode image in order to“register” the light pattern with the barcode image as previouslyexplained. After registration, the barcode image is captured byactivation of a mechanical trigger on the smartphone, an activationbutton on the display of the smartphone, or by lapse of a predeterminedperiod of time after registration of the light pattern with the barcodeimage as explained below. However, in some cases of blind modeoperation, the user may look through the display of the smartphone toassist in the guiding of the pattern of light at or about the barcodeimage. This mode of operation is known as blind mode targeted mode ofoperation since the display of the smartphone is used to “target” thepattern of light at or about the barcode image to generate theregistration required for blind mode operation as taught by thisdisclosure.

In targeted mode of operation, the light pattern on the surfacecontaining the barcode must hover over the barcode. As in blind mode,the user uses the light pattern generated by the aimer module of thisdisclosure as a pointer and points the light pattern at the surfacecontaining the barcode. In targeted mode, the light pattern must hoverover the barcode to be in registration unlike blind mode whereregistration may occur when the light pattern is shining outside thebarcode but still within the cone of viewing. As the user aims the lightpattern at the surface containing the barcode such that the lightpattern is hovering over the barcode and within the cone of viewing,there is a registration of the light pattern and the barcode in targetedmode according to this disclosure. As indicated in Table 1, the user mayemploy targeted mode operation with or without the use of the display.The most efficient manner of targeted mode operation involves a targetedmode blind operation without the use of the display. In this case, theuser would simply look at and “hover” the light pattern generated bythis disclosure over the barcode image in order to “register” the lightpattern with the barcode image as previously explained. Afterregistration, the barcode image is captured by activation of amechanical trigger on the smartphone, an activation button on thedisplay of the smartphone, or by lapse of a predetermined period of timeafter registration of the light pattern with the barcode image asexplained below. However, in some cases of targeted mode of operation,the user may look through the display of the smartphone to assist in theguiding of the pattern of light to hover over the barcode image. Thismode of operation is known as targeted mode targeted mode of operationsince the display of the smartphone is used to “target” the pattern oflight to “hover” over the barcode image to generate the registrationrequired for targeted mode operation as taught by this disclosure.

In display mode of operation, the user uses the display of thesmartphone to point the camera lens at the image. So long as the userpoints the camera lens at the image such that the light pattern andbarcode are both within the cone of viewing, there is a registration ofthe light pattern and the barcode in smartphone display mode accordingto this disclosure. The aimer module is not used when the smartphone isoperating in display mode of operation. Instead of using the lightpattern generated by the aimer module of this disclosure, the lamp ofthe smartphone is used conventionally to provide direct diffuse lightingfor illuminating the barcode image in order that the smartphone cancapture the barcode image.

Referring now to FIG. 3, aspects of the illustrative mobile device 10are shown. In this example, the mobile device 10 is outfitted with anaimer module that in FIG. 3 is depicted as aimer accessory 30.Generally, the aimer accessory 30 is tightly coupled to the mobiledevice 10 using conventional techniques. For example, the aimeraccessory 30 may be configured as an attachment piece for use inretrofitting of a given mobile device 10. Alternatively, the aimeraccessory 30 may be integrated into a given mobile device 10. Inembodiments in which the aimer accessory 30 is attached to the mobiledevice, the aimer accessory 30 may be attached by snap-fit connection asillustratively shown in FIGS. 23-26 and as explained below. In otherembodiments, the aimer accessory 30 may be an accessory that isintegrated into a protective case in which the mobile device 10 isstored. In other embodiments, the aimer accessory 30 may be an accessorythat is permanently affixed to the mobile device 10. For example, theaimer accessory 30 may be glued to the mobile device 10. In some otherembodiments, the aimer accessory 30 may be temporarily affixed to themobile device 10. For example, the aimer accessory 30 may include anembedded magnet that is magnetically attracted to the housing of themobile device 10. Some designs of the aimer accessory 30 provide formechanical retention of the aimer accessory 30 on the mobile device 10(for example, refer to FIG. 18). The aimer accessory 30 may also bereferred to herein simply as the “aimer 30.”

In the illustrative embodiment depicted in FIG. 3 (i.e., FIGS. 3A and3B), the aimer accessory 30 includes a body 35. The body 35 includes acollector 31 that surrounds the lens and sensor associated with thecamera 7. The body 35 further includes a collimator 34. The collimator34 provides for collimation of light from the lamp 9. The distal portion33 of the collimator 34 (see FIG. 3B) includes a grating 36. Generally,the grating 36 receives light from the lamp 9. The light may passthrough at least one optical element 32. Then at least one opticalelement 32 may provide for focusing light from the lamp 9 and/ordirecting the light through the grating 36. In the example shown, atleast one optical element 32 is disposed over the lamp 9. In someembodiments, at least one optical element 32 includes a light pipe. Inthe example shown in FIG. 3B, optical element 32 is shown as ahemispherical element. Illustrative embodiments with otherconfigurations of the light pipe are shown in FIGS. 10 and 21. In theexample shown in FIG. 3, the grating 36 illustratively includes twosubstantially parallel slits disposed in the distal portion 33 of thecollimator 34. As explained below, some example patterns that may bedisposed in the grating 36 include parallel slits, a substantiallyrectangular array of holes, a rectangular array of holes, and a patternof an icon. Some resulting light patterns (also referred to as a“pattern of light”) produced by the grating 36 are shown in FIG. 4.Generally, the grating 36 provides for casting a pattern of light 55onto a sample for imaging. In the examples discussed herein, the sampleincludes various forms of barcodes.

In some embodiments, at least one mirror is used with or without thegrating 36. In some other embodiments, at least one mirror is used withadditional optical elements as deemed appropriate. This is explainedfurther in connection with FIG. 20A-C.

Referring now to FIGS. 5 through 8, aspects of a process for imaging abarcode 50 with the aimer 30 are shown. In each of FIGS. 5 through 8, auser at some distance holds the mobile device 10 from the barcode 50.The software 22 (shown in FIG. 2) has been invoked and is causing themobile device 10 to attempt imaging of the barcode 50.

In FIG. 5, an illustrative barcode 50 is shown. The illustrative barcode50 is located within a field of view (FOV) 51. The field of view (FOV)51 represents the entire area that is naturally visible to the camera 7of the mobile device 10 (i.e., viewing angle of the camera). This isalso what the user sees on the display of a camera when doing a displaymode scan, as taught in the prior art. A shifted field of view (SFOV) 52is also shown. The shifted field of view (SFOV) 52 is a subset of thefield of view (FOV) 51 and is a result of processing by the specializedsoftware 22. The shifted field of view (SFOV) 52 represents an areawithin the field of view (FOV) 51 that aligns with a light pattern 55that is cast by the aimer accessory 30. This light pattern is what theuser uses to do a blind scan or targeted scan according to thisdisclosure. A scan area 56 is maintained within the shifted field ofview (SFOV) 52. Generally, the scan area 56 is a region of the shiftedfield of view (SFOV) 52 that is used by the software 22 to look for abarcode.

As shown in FIGS. 5A-D, the light pattern 55 correlates with theappearance of the grating 36 (see FIG. 3B). That is, referring back toFIGS. 3 and 4, it may be seen that the grating 36 illustrativelyincludes two parallel slits from which light is emitted. In each ofFIGS. 5 through 8, the light pattern 55 correlates with the twosubstantially parallel slits. Alternatively, the light pattern 55 may beany of the other patterns illustrated in FIG. 4, but also other shapesdepending on the implementation of the grating 36.

The software 22 makes use of the light pattern 55 cast by the aimeraccessory 30. Generally, once the software 22 has received a commandfrom the user to commence scanning, or a predetermined period of timehas elapsed after registration of the light pattern and the barcode, thesoftware 22 begins processing images collected from the camera 7 on acontinuing basis. When the light pattern 55 is appropriately manifestedwithin the scan area 56, the software 22 identifies a focal point 57(shown in FIG. 5C). In this example, the focal point 57 is centeredwithin the scan area 56. The software 22 recognizes the apparition ofthe barcode 50, and adjusts the focal point 57 to a start of the barcode50. Once an adjusted focal point 58 has been determined, the software 22will read the captured barcode 50. Once the captured barcode 50 has beenread, the software 22 may store data in the memory 21 (shown in FIG. 2).In some implementations, the software 22 can be configured to turn thelamp 9 on or off, as appropriate, for the capturing of images with thecamera 7,

FIG. 6 depicts an illustrative method for using the aimer module of thisdisclosure. The process starts 71 by user selection of mode ofoperation—namely, blind mode blind mode operation, blind mode targetedmode operation, targeted mode blind mode operation, targeted modetargeted mode operation, or display mode operation. After selection ofthe operational mode, the user points 72 the light near, around, or onthe barcode. In both blind mode blind mode operation and targeted modeblind mode operation, the user uses the light pattern generated by theaimer module of this disclosure as a pointer and points the lightpattern at the surface containing the barcode. The light patterngenerated by the aimer module guides the user on where to point thelight pattern. In both blind mode targeted mode operation and targetedmode targeted mode operation, the user uses the display of thesmartphone to point the light pattern generated by the aimer module ofthis disclosure at the surface containing the barcode. In display mode,the lamp of the smartphone is used conventionally to provide directdiffuse lighting for illuminating the barcode image in order that thesmartphone can capture the barcode image.

The decoding software of this disclosure takes care of decoding theimages of the barcode captured by the smartphone. In both blind modeblind mode operation and targeted mode blind mode operation, there is noneed for the user to look through the display of the smartphone whenoperating the scanning features of this disclosure in blind or targetedmode. In blind mode targeted mode operation, targeted mode targeted modeoperation, and display mode operation, the user will look through thedisplay to point the light at the barcode.

Further, in blind mode blind mode operation and blind mode targetedmode, it is only necessary for the user to aim the light patterngenerated by the aimer module at the surface containing the barcode suchthat the light pattern and barcode are both within the cone of viewing.This ensures registration of the light pattern and the barcode in blindmode according to this disclosure. In targeted mode blind mode operationand targeted mode targeted mode operation, it is necessary for the userto aim the light pattern at the surface containing the barcode such thatthe light pattern is hovering over the barcode and within the cone ofviewing. This ensures registration of the light pattern and the barcodein targeted mode according to this disclosure. In display mode, theaimer module is not used when the smartphone is operating in displaymode of operation. Instead of using the light pattern generated by theaimer module of this disclosure, the lamp of the smartphone is usedconventionally to provide direct diffuse lighting for illuminating thebarcode image in order that the smartphone can capture the barcodeimage.

A user may find the blind mode of operation most efficient when asurface contains only a single barcode. With a single barcode within thecone of vision, the specialized software of the mobile device, equippedwith an aimer module of this disclosure, recognizes there is only onebarcode to decode. The decoding software may invoke the scan any timeduring the process as previously explained. No further logic is needed.However, when a surface contains two or more barcodes, the software ofthe aimer module requires further logic to determine which barcode todecode. This disclosure provides this further logic within the targetedmode of operation by requiring the user to point the light patternwithin the barcode desired for decoding and keep the light pattern overthe barcode (i.e., hover over the barcode). The user then initiates atrigger to capture the image or the user hovers over the barcode for apredetermined period of time which may be set by the user.Illustratively, this period of time may be one-half second, but theexact time is a matter of design choice. It will be appreciated that auser may use the aimer module of this disclosure in targeted mode toalso scan a surface containing a single barcode. However, because thismode of operation requires the user to hover the light pattern over thebarcode, it may be a less efficient procedure for scanning a singlebarcode than scanning the barcode in blind mode of operation, but withmultiple barcodes present in a given area on a page, it may be thedesired method of reading the targeted barcode. With display mode, thesoftware of the aimer module requires further logic to determine whenthe user has lined up the camera lens with the barcode through thedisplay. This logic is illustratively provided by a trigger the user mayinitiate after the display indicates the camera lens is lined up withthe barcode.

The smartphone captures 73 one or more images and typically stores themin memory 21 (FIG. 2) of the smartphone. The capture may be initiated byuser activation of a mechanical trigger. Alternatively, the capture maybe initiated by user activation of a button on the smartphone, such asan on-screen software button or a physical re-programmed button. Inanother example, the capture may be automatically initiated (e.g.,software initiated) a predetermined period of time after registration ofthe light pattern and the barcode as explained in this disclosure. Ineither instance, software responsive to the initiation would begin thecapture of a series of images. Typically, the camera may grab 25 or 30frames of captured images a second. Some cameras may grab 60 frames asecond. The number of frames of images captured by the camera isdependent on the camera. In either event, the captured images are storedin memory 21 (FIG. 2) of the smartphone.

Starting with one captured image, which may be the first image capturedand stored in memory, the software of the aimer module will look 74 atan edge of the captured image. FIG. 7 depicts an example of a PDF417barcode useful for understanding the method of FIG. 6. The beginning andthe ending of the barcode, herein referred to as the edge of thebarcode, contains a start character and a stop character. The start andstop characters are used by the software of the aimer module of thisdisclosure to identify the type of barcode (i.e., its symbology). Hence,and referring back to FIG. 6, aimer module software looks 74 at the edgeof the captured image for the start and stop characters to identify thetype of barcode.

The aimer module software then determines the symbology of the barcode.In this regard, the aimer module software will illustratively access amemory map of symbologies such as depicted in FIG. 8 to match the startand stop characters it has determined to the start and stop charactersappearing in the table. If it finds a match, the aimer module softwarehas identified the symbology of the barcode.

If the aimer module software does not recognize the barcode type whetherbecause it has not identified a start and/or stop character or the startand/or stop characters it has identified do not match the start and stopcharacters in the memory map depicted in FIG. 8, the aimer module willdetermine 81 if it has another captured image of the barcode to furtheruse in this process of decoding the captured barcode. If the aimermodule software determines there are further images available for use inthe process, the aimer module software will advance 80 to the next imageand repeat steps 74 and 75. If the aimer module software determinesthere are no further images available for use in the process, the aimermodule software prompts 84 the user that the scan failed and the processends 86. This means that the user will need to begin the process over ifthe scan of the barcode remains of interest.

If the aimer module software recognizes the barcode type, the aimermodule software decodes 76 the barcode and then calculates and matches77 the check sum it has calculated with the check sum found in thepattern of the barcode. The aimer module software then determines 78 ifthe calculated error is correct (i.e., that the calculated check summatches the check sum in the pattern of the barcode). If the calculatederror value is not correct, the aimer module software will determine 83if it has another captured image of the barcode to further use in thisprocess of decoding the captured barcode. If the aimer module softwaredetermines there are further images available for use in the process,the aimer module software will advance 82 to the next image and repeatsteps 76, 77, and 78. If the aimer module software determines there areno further images available for use in the process, the aimer modulesoftware prompts 84 the user that the scan failed and the process ends86. This means that the user will need to begin the process over if thescan of the barcode remains of interest. If the aimer module softwaredetermines 78 that the calculated error is correct (i.e., that thecalculated check sum matches the check sum in the pattern of thebarcode), the aimer module software continues 79 the software programwhich can prompt the user that the scan was successful and the processends 86. The notification can be an audible, a vibration, a display LEDcoloring or blinking, or any combination of these or other physicalnotifications.

FIGS. 9 and 10 depict another embodiment of the aimer accessory 30. Inthis example, the aimer accessory 30 is configured to offset the opticalpath taken by the light that is emitted by the lamp 9. The offsetprovides for effectively redirecting light from the lamp 9 some distancefrom the camera 7. In this example, this is accomplished by using anoptical element 32 that includes a light pipe (shown in FIG. 10).Generally, the light pipe includes substantially transmissive material.In this example, the light pipe also includes reflective surfaces thatprovide for internal reflection within the light pipe.

FIGS. 11 and 12 provide yet another embodiment of the aimer accessory30. In this example, the aimer accessory 30 does not include a collector31. However, this embodiment of the aimer accessory 30 does include anoffset of the optical path taken by the light that is emitted by thelamp 9 (FIG. 1). Additionally, this embodiment of the aimer accessory 30includes a grating 36 having an array of holes arranged in asubstantially rectangular pattern.

Referring in particular to FIG. 12, aspects of the offset and theconsequence are shown in greater detail. In the mobile device, thecamera 7 is aligned with a camera axis, C. The lamp 9 is aligned with alight axis, L. By incorporation of an offset within the aimer accessory30 as taught by this disclosure, light emitted from the aimer accessory30 is redirected to a light shifted axis, LS. The resulting offset maybe measured as the distance between the light shifted axis, LS, and thelight axis, L. Accordingly, the offset angle, θ, between the cameraaxis, C and the effective light axis (which is now shifted light axis,LS, instead of the light axis, L) is increased. That is, the effectiverange, R, is increased. More specifically, a greater distance betweenthe mobile device 10 and the plane where the scan area 56 and the lightpattern 55 converge is realized.

Without the teachings of this disclosure, lamp 9 diffuses and emitslight across a wide range of angles with respect to light axis, L. Withthis disclosure, the light from lamp 9 is collimated and redirected tothe light shifted axis, LS, to improve the ability of the user to pointthe smartphone or mobile device's built-in camera at a barcode in orderto capture and decode the barcode. Because the light is shifted, thereis also less interference between the shifted light and the reflectedimage that is captured by the camera. This may in some circumstancesallow the camera to capture a better quality image than with ambientlight. While the effect of the offset is to increase the effectiverange, R, this increase was found to be negligible and to notsignificantly alter the advantages obtained by collimating the light andredirecting the collimated light to the light shifted axis, LS. Thetransformation of diffuse light from lamp 9 into a collimated beam oflight according to this disclosure effectively serves to modify thelighting from lamp 9 into a flashlight. Advantageously, this“flashlight” allows for blind and targeted aiming of the mobile deviceat, and efficient scanning of, a barcode according to the teachings ofthis disclosure.

Moreover, ambient light may oftentimes be sufficient to allow for thecapture of barcode images of a quality sufficient for decoding. Anadditional feature of this disclosure is that it provides additionallighting to the barcode surface which may improve the contrast of thedark and light barcodes and hence provide for capture of better qualitybarcode images.

FIG. 13 depicts an embodiment of the aimer accessory 30 that does notinclude a collector 31 but provides an offset. FIG. 13A is a perspectiveview. FIG. 13B is a top down view, and shows an interior of the aimeraccessory 30; it further shows a reflective surface 130 incorporatedtherein. At least another reflective surface (not shown) may be includedto direct light through the grating 36. FIG. 13C is a cutaway view ofthe aimer accessory 30. This embodiment of the aimer accessory 30 isreferred to as a “simple offset aimer.”

FIG. 14 depicts an embodiment of the aimer accessory 30 that includesthe collector 31 and does not have an offset. FIG. 14A is a perspectiveview; FIG. 14B is a top down view. FIG. 14C is a cutaway view of theaimer accessory 30, and better shows the optical element 32. In thisexample, the optical element 32 is a lens. This embodiment of the aimeraccessory 30 is referred to as a “basic aimer.”

FIG. 15 depicts an embodiment of the aimer accessory 30 that includesthe collector 31 and an offset. FIG. 15A is a perspective view; FIG. 15Bis a top down view. FIG. 15C is a cutaway view of the aimer accessory30, and better shows the optical element 32. In this example, theoptical element 32 includes a lens disposed within a light pipe. Thelight pipe is comparatively elongated (with reference to FIG. 16).However, it is not necessary that the light pipe extend completely tothe grating 36 in the distal portion 33. This embodiment of the aimeraccessory 30 is referred to as an “elongated offset aimer.”

FIG. 16 depicts an embodiment of the aimer accessory 30 that includesthe collector 31 and an offset. FIG. 16A is a perspective view; FIG. 16Bis a top down view. FIG. 16C is a cutaway view of the aimer accessory30, and better shows the optical element 32. In this example, theoptical element 32 includes a lens disposed within a light pipe. Thelight pipe is comparatively shortened (with reference to FIG. 15).Accordingly, this embodiment of the aimer accessory 30 is referred to asa “standard offset aimer.”

FIG. 17 depicts an embodiment of the aimer accessory 30 that includesthe collector 31 and an offset. FIG. 17A is a perspective view; FIG. 17Bis a top down view. FIG. 17C is a cutaway view of the aimer accessory30, and better shows the optical element 32. In this example, theoptical element 32 includes a lens disposed within a light pipe. Thelight pipe is of a continuous tube shape and includes a lens disposed atthe distal end. Accordingly, this embodiment of the aimer accessory 30is referred to as a “tube offset aimer.”

FIG. 18 depicts an embodiment of the aimer accessory 30 that includesthe collector 31, with no offset and a substantial body 35. FIG. 18A isa perspective view; FIG. 18B is a top down view. In this example, thebody 35 proves form fitting onto the mobile device 10. That is, in thisembodiment of the aimer accessory 30, the body 35 has been configured toclosely follow a particular configuration of the mobile device 10.Accordingly, this embodiment of the aimer accessory 30 is referred to asa “fitted aimer.”

FIG. 19 shows an instance of a barcode reader software 200 for providingsome of the functionality herein described. The instance includes anengine 201, a scanning software 214, a decoder software 217, a datastorage software 212, a library software 210, a user interface software,a hardware controller software 215, and a communication interfacesoftware 216.

The scanning software 214 includes the executable instructions forperforming the scanning functions of registration and capturing abarcode image as described in FIG. 6. The scanning software 214 willreceive data from the camera 7 and evaluate the received data forpresence of a barcode. The evaluation may include identification of theshifted field of view (SFOV) 52, the scan area 56, and searching forpresence of the barcode 50 that is in registration with the lightpattern 55. When the scanning software 214 has identified theappropriate requirements for data collection, the scanning software 214will capture the barcode 50.

The decoder software includes the executable instructions fortransforming the barcode image data represented by the electricalsignals into an encoded ASCII character data string.

The data storage software 212 includes the executable instructions forstoring and retrieving captured barcode images and other data in amemory. The library software 210 includes the executable instructionsfor storing and retrieving information such as symbology type from alibrary registry within the memory. Additionally, the library registrymay also include information regarding a variety of aimer accessories30. For example, a user may wish to exchange aimer accessories 30 whilein the field, like to exchange a tube offset aimer of FIG. 17 for thebasic aimer of FIG. 14. Accordingly, the user may remove a first aimeraccessory 30 (e.g., the tube offset aimer) from a mobile device 10 andplace a second aimer accessory 30 (e.g., the basic aimer) onto themobile device. When this occurs, the user may communicate the secondaimer accessory type to the engine software 201 using the graphical userinterface rendered by the user interface software 211. The enginesoftware 201 may then employ the library software 210 to reference datastored in the library registry regarding the second aimer accessory 30for use in configuring the smartphone and software accordingly.Alternatively, the hardware controller software 215 may detect theattachment of the second aimer accessory 30 and prompt the enginesoftware 201 to cause the user interface software 211 to render on thedisplay a selection of settings for aimer accessories useable with thesmartphone. In the specific example, the settings would include thesettings for the tube offset aimer and the settings for the basic aimer.On user selection of the setting for the basic aimer, the scanningsoftware 214 will then adjust scanning functions accordingly.

In another embodiment, the instance of a barcode reader software 200 mayrecognize a specific aimer module shape and if recognized for a specifictimeframe while hovering over a specific barcode for a programmed amountof time (˜500 msec or 1 sec), then this triggers a barcode scan andinitiates a decode of the barcode data.

The user interface software includes the executable instructions fordisplaying a graphical user interface on the display for configuring theinstance of the barcode reader software 200 and for rendering images,such as an image of the barcode on the display of the smartphone. Forexample, user interface software 211 may generate text, alertinformation, auditory signals, alarms, warnings, pictures, graphics, orother types of output. In some embodiments, output of the interfacesoftware 211 may be used to invoke other functions. For example, outputof the interface software 211 may be sent via communication interfacesoftware 216 to a printer, or it may be sent to a smartphone to initiatea phone call, or sent to any computing device to perform some otherfunction.

The hardware controller software 215 includes the executableinstructions for controlling the hardware of the smartphone such ascontrolling the camera lens to bring a barcode image into focus,energizing the lamp, controlling the display to render images,controlling the speaker of the smart phone to prompt a user, and so on.

The communication interface function 216 includes the executableinstructions for communicating data to or from a remote device. Thecommunicating to a remote device may include conducting a query of aremote source, such as a database, for more comprehensive information.The query may be received by the communication interface function 216from the user through the user interface software 211. Similarly, aremote user may communicate information over the communication interface216 to the smartphone. Thus, for example, a smartphone may be remotelyprogrammed with software updates and updates to the database, such asthe table of symbologies. Programming may occur over-the-air.Alternatively, the smart phone may be tethered to a remote device via acommunication cable to provide such remote programming or bi-directionalcommunication between the smart phone and the remote device. The remotedevice may be a computing device, for example, another smart phone, adesktop computer, or server, including a cloud server, capable ofcommunicating with the smart phone that is operating according thisdisclosure.

The engine 201 includes the executable instructions that coordinate theoperation of the foregoing and other programs on the smartphone.

The software 200 described in connection with FIG. 19 may be provided toa mobile device by a specialized application. For example, a mobileapplication including the foregoing functionalities for performing thisdisclosure is typically downloaded to a smartphone, but also may bepreloaded. Alternatively, the software may be functionality embeddedinside the operating system.

By virtue of the registration process of the light pattern 55 of thisdisclosure with a barcode 50 on a target as explained in thisdisclosure, an appropriately equipped mobile device 10 is capable ofautomatic scanning and reading of barcodes. That is, the mobile device10 that is so equipped does not require human intervention to carefullyfocus the camera through the display 5. The user need not look throughthe view finder projected on the display to focus the image to becaptured by the mobile device. Instead, in blind mode blind modeoperation and target mode blind mode operation, the user need only pointthe collimated light that is generated according to this disclosure atthe barcode. Accordingly, the teachings herein provide for enablement of“blind” and “targeted” blind mode scanning. That is, the blind ortargeted scanning according to this disclosure permits a user to read abarcode without viewing and focusing of the device camera through use ofthe display 5 (shown in FIG. 1). More specifically, the user only needsto “aim” or “point” the mobile device using the aimer module at thebarcode and the mobile device will read the barcode. Of course, thisdisclosure also provides for blind mode targeted mode and targeted modetargeted mode where the display of the smartphone is used by the user toassist in lining up the pattern of light with the barcode image astaught by this disclosure. In addition, this disclosure also providesfor a scanning operation performed in display mode where the aimermodule of this disclosure is not used in the scanning operation; rather,diffuse lighting from the conventional smartphone is used to illuminatea barcode in order to capture the barcode image using conventionalscanning techniques.

In some embodiments, the software 22 of the code reader 200 depicted inFIG. 19 may be developed on a remote computer, such as a personalcomputer. The software 22 may then be downloaded to the mobile device.

FIG. 20A is a perspective drawing of yet another alternative embodimentof this disclosure. In this embodiment, a pair of mirrors 220, 222 areused to redirect light away from the axis of the optical path of lightemitted from lamp 221 and to a target. In particular, mirror 220 changesthe direction of the optical path of light emitted from lamp 221 fromlight axis, L to a first light shifted axis, LS and directed to mirror222. Mirror 222 redirects the reflected beam of light to a second lightshifted axis, LS to the target. In this example, the reflective surfaceof mirror 222 is in the shape of a hand pointing a finger so that thebeam of light reflected from mirror 222 to the target includes thisimage. FIG. 20B depicts the illumination of the barcode target with theimage contained in the pattern of light 55, namely collimated light inthe shape of a hand pointing a finger. A user may line up the finger ofcollimated light to an edge of the barcode whereupon the barcode may becaptured and processed as explained above. FIG. 20C shows an alternativeembodiment of FIG. 20A wherein the reflective surface of mirror 222 isin the shape of the reversed spelling of the word “HELLO” (spelled“OLLEH”).

FIG. 21 depicts illustrative embodiments of light pipes that may be usedwith the aimer accessory 30. Each light pipe redirects the optical pathof light from light axis, L to a light shifted axis, LS as shown whereinthe barcode is easily captured and processed.

FIG. 22 depicts an illustrative method for aimer scanning 230 (e.g.,blind mode blind mode operation, blind mode targeted mode operation,targeted mode blind mode operation, and targeted mode targeted modeoperation). According to the method, light is emitted 231 from a lamp ofthe mobile device along a first optical path toward a barcode target.The first optical path defines a light axis, L. The optical path of theemitted light is then changed 232 from the light axis, L, to a secondoptical path that is oblique to the barcode target. The optical path ofthe emitted light is then changed again 233 from the oblique opticalpath to a third optical path that is directed at the barcode target. Thethird optical path defines a light shifted axis, LS. Finally, the imageof the barcode target is captured 234 by the mobile device.

Referring now to FIGS. 23 through 26, aspects of an additionalembodiment of the aimer accessory 30 are shown. In the example shown,the aimer accessory 30 includes a retainer 38. Generally, the retainer38 provides for coupling of the aimer module body onto the mobile device10 or to an external protective case surrounding mobile device 10. Inthe example shown, the retainer 38 includes an arm that extends upwardand over the top of the mobile device 10 and terminates with a clip 37(see FIG. 26) on the front of the mobile device 10. Accordingly, bycooperation of the retainer 38 with the clip 37 and the opposing body35, this embodiment of the aimer accessory 30 may be effectively clippedonto the mobile device 10. Accordingly, this embodiment of the aimer 30is referred to as a “clip-on aimer.”

In various embodiments, the retainer 38 provides a clamping force to themobile device 10 or to an external protective case surrounding mobiledevice 10. In some embodiments, the clamping force is realized by havingopposing retainers 38. Opposing retainers 38 may be realized by havingone retainer configured for retention on a left side of the mobiledevice 10 or protective case with the opposing retainer 38 configuredfor retention on a right side of the mobile device 10 or protective case(not shown). In some embodiments, the retainer 38 includes the detents,nipples, ridges or other features as may be known in the art to assistwith retention and registration or alignment with mobile device 10.

In some embodiments, such as the one shown in FIGS. 23 through 26, theclip-on aimer is further stabilized by having portions that conform tothe shape of the mobile device 10 or protective case for mobile device10. For example, the clip-on aimer includes a deep-well collector 31that conforms to the shape of the mobile device 10 or to the protectivecase surrounding mobile device 10. Additionally in this embodiment, theclip-on aimer includes a body 35 to conform to curved surfaces of themobile device 10.

FIG. 27 depicts an illustrative method for retrofit of a mobile devicewith the aimer accessory of this disclosure The method for modificationof the mobile device 260 includes selecting an aimer accessory 261. Theaimer accessory selected may include any one of the aimer accessories asdiscussed herein, a combination thereof, or an aimer accessory thatincludes other features than those disclosed herein. After completingthe selection of the aimer accessory 261, the user performs affixing ofthe aimer accessory 262. Affixing of the aimer accessory 262 generallycalls for one of temporarily affixing or permanently affixing the aimeraccessory to the mobile device 10 or to the protective case surroundingmobile device 10.

An aimer accessory according to this disclosure can be secured to amobile device, or a case for a mobile device, in various ways. In someembodiments, an aimer accessory (e.g., the aimer accessory 30) can besecured directly to a mobile device or to a case using adhesives,adhesive strips (e.g., double-sided tapes), magnetic devices, fasteners(e.g., screws), and so on. In some embodiments, a clip-like tab such asthe retainer 38 (see, e.g., FIGS. 25 and 26) can be used to physicallyengage a mobile device or case in order to secure the aimer accessory inplace.

In some embodiments, an aimer accessory can be formed from an attachmentbase and an attachment body that are configured to be removably securedtogether. With this type of arrangement, the attachment base can besecured to a mobile device or case (e.g., using adhesives, adhesivestrips, magnetic devices, fasteners, and so on) independently of theattachment body. The attachment body, which can be configured to includean optical device such as a light pipe or arrangement of mirrors, canthen be secured to the attachment base for use with the mobile device.This can be useful, for example, in order to allow for reliable andrepeatable orientation of the attachment body—and the included opticaldevice—relative to a camera or light source of the mobile device,without necessarily requiring a permanent engagement between theattachment body and the mobile device or case.

Specific examples of this type of arrangement are discussed below in thecontext of direct attachment to a mobile device and in the context ofattachment to a mobile device via attachment to a case for the mobiledevice. It will be understood, however, that other arrangements arepossible and that the principles discussed below (e.g., securing anattachment body with an optical element to a mobile device or case viaattachment of the attachment body to an attachment base) can be appliedto other embodiments, including various embodiments discussed above(e.g., the various arrangements of the aimer accessory 30 illustrated inFIGS. 3A, 3B, 9-18B, and 23-26). Likewise, aspects of the examplearrangements of the aimer accessory 30 discussed above can beimplemented with the aimer accessories discussed below, including assubstitutes for aspects of the aimer accessories discussed below (e.g.,substitution of a light pipe as discussed above for a mirror arrangementas discussed below), or as supplementary aspects of the aimeraccessories below.

An aimer accessory 300 for a mobile device is illustrated in FIGS.28-33. Generally, the aimer accessory 300 includes an attachment base302 configured for attachment to a mobile device or to a case for themobile device (not shown in FIGS. 28-33). The aimer accessory 300 alsogenerally includes an attachment body 304 that is configured to beremovably secured to the attachment base 302 and can include one or moreoptical devices (e.g., mirror arrangements or light pipes). In this way,for example, when the attachment base 302 is secured to a mobile deviceor a case, the attachment body 304 can be temporarily disposed for usewith a camera of the mobile device by securing the attachment body 304to the attachment base 302.

In the embodiment illustrated, the attachment base 302 is formed as asingle-piece body that includes a relatively large camera opening 306configured for alignment with a camera of a mobile device (not shown inFIGS. 28-33). The camera opening 306 is generally rectangular, but alsoincludes a rounded indent 308 at one end. A raised lip 310 partlysurrounds the camera opening 306 and is in turn partly surrounded by ashoulder 312. As illustrated in FIGS. 29 and 30 in particular, theshoulder 312 further extends around most of the perimeter of theattachment base 302, interrupted by a side opening 314 on the attachmentbase 302.

The attachment base 302 also includes a light-source opening 316.Generally, the light-source opening 316 is disposed relative to thecamera opening 306 so that when the camera opening 306 is aligned with acamera or camera lens of a mobile device, the light-source opening 316is also appropriately aligned with a light source of the mobile device(e.g., a light source such as the optical element 32 illustrated in FIG.3B). In the embodiment illustrated, the light-source opening 316 isgenerally adjacent to the camera opening 306, although otherconfigurations are possible.

In some embodiments, a light-source opening on an attachment base can beshaped to partly mask a light source on a mobile device. This can beuseful, for example, if a light source on a mobile device is expected tobe overly bright, or if a light source on a mobile device includesmultiple light-emitting elements (e.g., LEDs), some of which it may bedesirable to mask. In the embodiment illustrated, the light-sourceopening 316 is configured as a generally semi-circular or semi-ovularopening with one wall 316 a of the light-source opening 316 configuredas a solid blocking feature. This can be useful, for example, for usewith light sources that include a white-light LED and a yellow-lightLED, in order to block light from the yellow-light LED while allowinglight from the white-light LED to pass through the attachment base 302into the attachment body 304.

The attachment base 302 can also generally include structures to assistin removably securing the attachment body 304 to the attachment base302. In the embodiment illustrated, for example, the attachment base 302includes a set of attachment openings 318 and 320, each of whichincludes a respective overhang 322 and 324 formed by partially angledfeatures 322 a and 324 a on an upper portion the attachment base 302. Inthe embodiment illustrated, the ends of the attachment openings 318 and320 are offset from each other along a length direction 326, as are theends of the overhangs 322 and 324 and the features 322 a and 324 a. Inother embodiments, however, other configurations are possible.

Each of the attachment openings 318 and 320 is also generally adjacentto a respective indent 328 and 330, which are disposed on an oppositeside of the respective attachment openings 318 and 320 from therespective overhangs 322 and 324. In the embodiment illustrated, theindent 328 is configured as a rounded indent spaced apart from theattachment opening 318 and the indent 330 is configured as a roundedindent extending into an edge of the attachment opening 320. In otherembodiments, however, other configurations are possible.

Still referring to FIGS. 28-33, the attachment body 304, which isgenerally configured for removable attachment to the attachment base302, includes a housing portion 340 generally formed as a single-pieceshell 342 that is configured to enclose and support part or all of anoptical device. For example, the shell 342 can be configured to encloseand support a mirror assembly or a light pipe for use with a lightsource on a relevant mobile device.

In the embodiment illustrated, the shell 342 is configured to enclose anoptical device configured as a mirror assembly including mirrors 344 and346 and lens 348 (see FIGS. 31-33). To this end, the shell 342 includesinternal shelves 350 and a lens opening 352 surrounded by an internalshoulder 352 a, which can generally support and align the mirror 344 andthe lens 348, respectively. Further, the shell 342 includes internalstruts 354 configured to support and align an insert 356. The insert 356includes a shelf 358 and support surface 360 for the mirror 346, as wellas an angled support rib 362 extending away from the support surface360.

As illustrated in FIGS. 32 and 33 in particular, the insert 356 can beinserted into the shell 342 until the shelf 358 engages respective endsof the struts 354 and the support rib 362 engages an interior surface ofan end wall 342 a of the shell 342. The insert 356 can then be securedin place in various ways, including with adhesives, with a press-fitengagement, with detents or similar other features (not shown) and soon. In this way, for example, the mirror 346 can be appropriatelyaligned with the mirror 344 and the lens 348 (or other optical elements)without requiring excessively complex internal geometry or assemblyprocedures for the shell 342.

Generally, the shell 342 can be configured for relatively low-profileattachment to a mobile device or case, and can include various featuresto facilitate use of the attachment body 304 with a camera of a mobiledevice. For example, a wall 342 b of the shell 342 that is to bedisposed generally adjacent to a field of view of a camera can beconfigured with an angled geometry so that interference with cameraoperation by the shell 342 can be minimized. The angled geometry of thewall 342 b can also, for example, help to appropriately support one ormore components of an optical device within the shell 342, such as themirror 344 (e.g., as discussed above).

The attachment body 304 can also generally include features forremovably securing the attachment body 304 to the attachment base 302.In the embodiment illustrated, for example, the attachment body 304includes a set of attachment arms 364 and 366 extending out of a mainopening 342 c of the shell 342. The free end of each of the attachmentarms 364 and 366 includes a respective protrusion 368 and 370, each ofwhich can generally be configured with a complimentary (e.g.,complimentarily angled) geometry to a corresponding one of the overhangs322 and 324 on the attachment base 302.

In the embodiment illustrated, the ends of the protrusions 368 and 370are offset from each other along the length direction 326, as are theends of the attachment arms 364 and 366 generally. This arrangement canbe similar to the offset arrangement for the attachment openings 318 and320 and the overhangs 322 and 324, as discussed above. In otherembodiments, however, other configurations are possible.

The attachment body 304 can also include features for engaging theindents 328 and 330 of the attachment base 302. In the embodimentillustrated, for example, each of the attachment arms 364 and 366 isdisposed near, but spaced apart from, respective detents 372 and 374(see FIG. 30, in particular). Generally, each of the detents 372 and 374can exhibit a complimentary geometry to a corresponding one of theindents 328 and 330, so that the detents 372 and 374 can be seatedappropriately within the indents 328 and 330 when the attachment body304 is secured to the attachment base 302.

The attachment body 304 can also include various other features. In theembodiment illustrated, for example, the shell 342 includes an extendedlower portion 376 that extends generally below a remainder of the shell342 (e.g., a peripheral lower surface 378 of the shell 342), as well asan attachment lip 380 extending generally below the remainder of theextended lower portion 376. Generally, the attachment lip 380 caninclude a complimentary (e.g., complimentarily curved) geometry as theindent 308 in the camera opening 306 of the attachment base 302. Inother embodiments, however, other configurations are possible.

In the embodiment illustrated, the attachment body 304 also includes anattachment tab 382, which can help to secure the attachment body 304directly to a mobile device or case. In the embodiment illustrated, theattachment tab 382 exhibits a generally curved profile extending awayfrom and below the shell 342, with an elongated detent 384 near a freeend of the attachment tab 382 to engage a corresponding groove on a caseor other object.

As illustrated in particular in FIGS. 31-33, the features describedabove can facilitate a user removably securing the attachment body 304to the attachment base 302 with relative ease and rapidity. Generally,to attach the attachment body 304 to the attachment base, the attachmentarms 364 and 366 can be aligned with and inserted into the attachmentopenings 318 and 320, and the attachment lip 380 can be aligned with andinserted into the camera opening 306. The attachment body 304 can thenbe slid along the length direction 326 until the protrusions 368 and 370are seated in the overhangs 322 and 324 (and against the undersideangled features 322 a and 324 a), the detents 372 and 374 are seated inthe indents 328 and 330, and the attachment lip 380 is seated in theindent 308 of the camera opening 306.

As also noted above, the attachment openings 318 and 320 are offset fromeach other along the length direction 326, as are the protrusions 368and 370 and the attachment arms 364 and 366. This arrangement can resultin a relatively stable connection between the attachment body 304 andthe attachment base 302, due to contact points between the protrusion368 and the angled feature 322 a being offset from contact pointsbetween the protrusion 370 and the angled feature 324 a along both thelength and the width of the assembly.

Other relative offsets of various features can also be useful. Forexample, as illustrated in FIG. 33 in particular, when the attachmentbody 304 and the attachment base 302 are firmly (and removably) securedtogether, bottom surfaces 364 a and 366 a of the attachment arms 364 and366 are offset along a height direction 386 from a bottom surface 302 aof the attachment base 302. This can be useful, for example, in order toprevent the attachment arms 364 and 366 from sliding along, andpotentially scratching, a surface against which the bottom surface 302 aof the attachment base 302 is seated (e.g., a surface of a mobile device(not shown in FIG. 33)).

In some aspects, a lack of offsets between different parts of the aimeraccessory 300 can also provide useful stability. For example, asillustrated in FIGS. 31 and 33 in particular, when the attachment body304 and the attachment base 302 are firmly secured together, a bottomsurface 380 b of the attachment lip 380 of the shell 342 can begenerally flush with the bottom surface 302 a of the attachment base302. Accordingly, the attachment lip 380 can engage with a surfaceagainst which the bottom surface 302 a of the attachment base 302 isseated (e.g., a surface of a mobile device (not shown in FIG. 31)) inorder to further stabilize the attachment body 304 and the aimeraccessory 300 generally.

With the attachment body 304 and the attachment base 302 assembled asillustrated, the camera opening 306 of the attachment base 302 is leftgenerally open, while the light-source opening 316 of the attachmentbase 302 is fully enclosed (at least on one side of the attachment base302) by the shell 342 of the attachment body 304. Further, thelight-source opening 316 is generally aligned with one or morecomponents of the optical device of the attachment body 304 (e.g., withthe first mirror 344 within the shell 342). Accordingly, the assembledaimer accessory 300 can be used with a camera of a mobile device tocapture images via the camera opening 306. Further, due to the enclosureof the light-source opening 316 by the shell 342, the assembled aimeraccessory 300 can be used both to route light from a light source of themobile device through the optical device of the attachment body 304, andto otherwise generally occlude the light source to prevent unwantedillumination of external objects.

In order to use the aimer accessory 300 with a mobile device having acamera and a light source, the aimer accessory 300 can be secured inplace relative to the mobile device with the camera opening 306 alignedwith the camera, and with the light-source opening 316 aligned with thelight source. In some embodiments, this alignment can be obtainedthrough the use of a case configured to engage the attachment base 302.

As illustrated in FIG. 34, for example, a case 400 for use with theaimer accessory 300 and a mobile device (not shown in FIG. 34) caninclude a camera opening 402 that is generally configured to align witha camera and a light-source of the mobile device when the mobile deviceis inserted into the case 400. The camera opening 402 exhibits agenerally complimentary peripheral profile as the attachment base 302,with an internal shoulder 404 that is generally complimentary to theshoulder 312 of the attachment base 302 (see, e.g., FIG. 29).Accordingly, as illustrated in FIG. 35, the attachment base 302 can beinserted into the inside of the case 400, in alignment with the cameraopening 402, so that engagement of the shoulder 312 with the shoulder404 prevents the attachment base 302 from being removed from the case400 via the camera opening 402.

As illustrated in FIG. 36, when a mobile device 406 is then insertedinto the case 400, the mobile device 406 can seat against the bottomsurface 302 a of the attachment base 302 (see also FIGS. 29 and 35),thereby cooperating with the shoulder 404 to secure the attachment base302 within the case 400 and in alignment with the camera opening 402. Asalso illustrated in FIG. 36, with the attachment base 302 and the mobiledevice 406 thus inserted into the case 400, a camera lens 408 of themobile device 406 can be aligned with the camera opening 306 in theattachment base 302 so that the attachment base 302 generally does notobstruct image capture with the camera lens 408.

Further, in the embodiment illustrated, the indent 308 in the cameraopening 306 is aligned with a microphone 410 (or other similarly locatedfeature) on the mobile device 406, so that the microphone (or otherfeature) can still be used (e.g., for noise-cancellation purposes) evenwith the attachment base 302 in place. Also in the embodimentillustrated, the light-source opening 316 is generally aligned with alight source 412 of the mobile device 406, but with the blocking featureformed by the wall 316 a of the light-source opening 316 partiallyoccluding the light source 412 (e.g., a yellow-colored portion thereof).Accordingly, when the attachment body 304 is secured to the attachmentbase 302, some but not all of the light from the light source 412 canpass into the shell 342 for manipulation by the optical device therein(e.g., the assembly of the lens 348 and the mirrors 344 and 346).

As illustrated in FIG. 37, once the mobile device 406 and the attachmentbase 302 have been secured in the case 400, the attachment body 304 canbe removably secured to the attachment base 302 (e.g., as describedabove) for use with the camera lens 408 and the light source 412 of themobile device 406. As also illustrated in FIG. 37, to further secure theattachment body 304 relative to the mobile device 406, the attachmenttab 382 of the attachment body 304 can be disposed to wrap onto a side(e.g., the top side) of the case 400, with the detent 384 (see, e.g.,FIG. 33) engaging a groove 414 on the case 400.

In other embodiments, other configurations are possible, includingvariations on the features discussed above. For example, in someembodiments, one or more attachment arms can be provided on anattachment base rather than on an attachment body, and one or morecorresponding attachment openings can be provided on the attachment bodyrather than on the attachment base. Similarly, for example, one or morefeatures similar to the detents 372 and 374 can be provided on anattachment base rather than on an attachment body, and one or morecorresponding indents can be provided on the attachment body rather thanon the attachment base. In some embodiments, an attachment base can beconfigured to entirely occlude a light source of a mobile device.

In other embodiments, an attachment base can also (or alternatively) beconfigured to attach in different ways to a case (or mobile device). Forexample, an attachment base can be configured to attach to the exteriorof a case rather than through engagement with an internal shoulder ofthe case.

An attachment body 430 for another aimer accessory is illustrated inFIGS. 38 and 39. Similarly to the attachment body 304, the attachmentbody 430 can generally include one or more optical devices (e.g., mirrorarrangements) and is configured to be removably secured to an attachmentbase (as discussed below) that can in turn be secured to a mobile devicewith a camera (not shown in FIGS. 38 and 39).

In the embodiment illustrated, the attachment body 430 includes ahousing portion generally formed as a single-piece shell 432 that isconfigured to enclose and support part or all of one or more opticaldevices. For example, the shell 432 can be configured to enclose andsupport a mirror assembly or a light pipe for use with a light source ona relevant mobile device.

Also in the embodiment illustrated, the shell 432 is configured toenclose an optical device configured as a mirror assembly with variousmirrors (not shown) and a lens (not shown). Accordingly, the shell 432includes internal support surfaces 434 and 436 to support variousmirrors (not shown), as well as a lens opening 438 configured to receivea lens (not shown). The lens and mirrors (not shown) can be securedwithin the shell 432 in various ways, including through the use ofadhesives, press-fit engagement, and so on.

Generally, the shell 432 can be configured for relatively low-profileattachment to a mobile device or case, and can include various featuresto facilitate use of the attachment body 304 with a camera of a mobiledevice. For example, a wall 432 a of the shell 432 that is to bedisposed generally adjacent to a field of view of a camera can beconfigured with an angled geometry so that interference with cameraoperation by the shell 432 can be minimized. The angled geometry of thewall 432 a can also, for example, help to appropriately support one ormore components of an optical device, such as a mirror, within the shell432.

The attachment body 430 can also generally include features forremovably securing the attachment body 430 to an attachment base (e.g.,an attachment base as discussed below). For example, the shell 432 caninclude a pair of support legs 440 extending downwardly from a main body442 of the shell 432, with a set of internal grooves 444 and 446. In theembodiment illustrated, the grooves 444 and 446 extend partly along thelength of the support legs 440 from an area below an overhang 448 at oneend of the support legs 440 to tapered ends 444 a and 446 a of therespective grooves 444 and 446.

The attachment body 430 can also include various other features. In theembodiment illustrated, for example, the shell 432 includes a roundedopening 452 at a bottom end of the wall 432 a, and a inwardly curvingchannel 454 extending along part of the wall 432 a to the opening 452.The shell 432 also includes an internal recess 450 extending into theinterior of the shell 432 from within the overhang 448.

An attachment base 460 for use with the attachment body 430 isillustrated in FIGS. 40 and 41. In the embodiment illustrated, theattachment base 460 is formed as a single-piece body that generallytapers in height along a length direction 462 from a raised end 460 b toa lower-profile end 460 b. A generally rounded opening 464 is providedat the lower-profile end 460 b, as is a light-source opening 466. In theembodiment illustrated, the light-source opening 466 is configured as agenerally circular or ovular opening with a generally semi-circular orsemi-ovular blocking feature 468 occluding approximately half of thelight-source opening 466. As such, as illustrated in FIG. 41, thelight-source opening 466 present a generally semi-circular orsemi-ovular aperture for admission of light (e.g., from a light sourceof a mobile device).

The attachment base 460 can also generally include structures to assistin removably securing the attachment body 430 to the attachment base460. In the embodiment illustrated, for example, the attachment base 460includes a set of attachment rails 470 and 472, a pair of grip arms 474and 476, and a cantilevered locking tab 478. The attachment rails 470and 472 generally extend along part of the length of the attachment base460 between respective end walls of the grip arms 474 and 476 andrespective tapered ends 470 b and 472 a of the attachment rails 470 and472. The grip arms 474 and 476 are configured to be generally rigid andinclude respective sets of raised grip features 488, which can assist auser in manually positioning or otherwise holding the attachment base460. The locking tab 478 extends generally between the grip arms 474 and476 and is configured to be elastically deformable relative to theremainder of the attachment base 460 (e.g., relative to the grip arms474 and 476) when the locking tab 478 is manually subjected to force ator near a free end 478 a. An upper surface of the locking tab 478includes a detent 480, with a flattened locking wall 480 b and a slopedand rounded entrance wall 480 b.

As illustrated in FIG. 41 in particular, the attachment base 460includes a generally flat bottom surface 482. As such, for example, theattachment base 460 can be secured directly to a flat surface of amobile device (or case) using adhesives or adhesive strips (e.g.,double-sided tape) or other attachment mechanisms (e.g., magnets). Inother embodiments, other configurations are possible. For example, theattachment base 460 can be provided with a shoulder similar to theshoulder 312 of the attachment base 302 (see, e.g., FIG. 29) so that theattachment base 460 can engage a case for a mobile device.

Referring in particular to FIG. 42, in preparation for securing theattachment body 430 to the attachment base 460, the lower-profile end460 b of the attachment base 460 can be aligned with the overhang 448 onthe attachment body 430 (or vice versa), with the attachment rails 470and 472 (only the attachment rail 470 is shown, in dotted relief, inFIG. 42) generally aligned with the grooves 444 and 446 (only the groove446 is shown, in dotted relief, in FIG. 42). The attachment body 430 canthen be moved relative to the attachment base 460, as indicated by arrow484, in order to move the attachment rails 470 and 472 into therespective grooves 444 and 446.

As the attachment rails 470 and 472 are moved farther into the grooves444 and 446, the detent 480 on the locking tab 478 can come into contactwith a rear wall 432 b of the shell 432. With continued movement of theattachment body 430 in the direction of the arrow 484, the angledprofile of the entrance wall 480 b of the detent and the movement of theattachment body 430 relative to the attachment base 460 can then deflectthe locking tab 478 downward (e.g., as indicated by arrow 486). Withfurther relative movement of the attachment body 430 and the attachmentbase 460, the detent 480 can clear the wall 432 b, such that the lockingtab 478 is released from the noted deflection and the detent 480 canmove into the recess 450 in the shell 432. The locking wall 480 b of thelock can then seat against an interior surface of the wall 432 b togenerally prevent disconnection of the attachment body 430 from theattachment base 460 by movement of the attachment body 430 opposite thedirection of arrow 484.

In some embodiments, the attachment rails 470 and 472 and the grooves444 and 446 can be dimensioned so that the detent 480 clears the wall432 b substantially simultaneously with the tapered ends 470 b and 472 aof the attachment rails 470 and 472 reaching the tapered ends 444 a and446 a of the grooves 444 and 446. Accordingly, the detent 480, the wall432 b, the grooves 444 and 446, and the attachment rails 470 and 472 cancollectively and snugly secure the attachment body 430 to the attachmentbase 460.

To remove the attachment body 430 from the attachment base 460, thelocking tab 478 can be deformed downward (e.g., with manual forceapplied at the free end 478 a) until the detent 480 clears the wall 432b. The attachment rails 470 and 472 can then be slid free of the grooves444 and 446 and the attachment body 430 generally separated from theattachment base 460.

As also illustrated in FIG. 42, when the attachment body 430 is fullysecured to the attachment base 460, the light-source opening 466 of theattachment base 460 is generally aligned with the internal supportsurface 434 of the attachment body 430. Accordingly, light passing intothe attachment body 430 via the light-source opening 466 can generallyfall on a mirror (not shown) or other optical device disposed on thesupport surface 434. Further, the lower-profile end 460 b of theattachment base 430 generally extends into the opening 452 in the shell432, with the rounded opening 464 of the attachment base 460 beinggenerally aligned with the channel 454 in the shell 432.

FIG. 43 illustrates an aimer accessory 490 formed from the attachmentbody 430 and the attachment base 460, as installed for use with a mobiledevice 492 that includes a camera lens 494 and a microphone 496 (e.g.,for noise-cancellation functionality). Generally, the attachment base460 can be installed on the mobile device 492 (e.g., using an adhesivestrip (not shown)) so that the lower-profile end 460 b of the attachmentbase 460 is adjacent to, but does not overlap, the camera lens 494 andso that the opening 464 is generally aligned with the microphone 496.The attachment body 430 can then be secured to the attachment base 460(e.g., as described above), with the opening 452 providing clearance forthe camera lens 494 as the attachment body 430 is slid onto theattachment base. With the attachment body 430 thus secured, the aimeraccessory 490 generally encloses completely a light source (not shown)of the mobile device 492, so that light from the light source isprevented from illuminating surrounding objects except by passingthrough the attachment body 430. Further, despite this generallycomplete enclosure with regard to the light source, the alignment of thechannel 454 with the opening 464 still allows for the microphone 496 toremain exposed for operation.

As also noted above, different arrangements are possible for an opticaldevice included in an aimer accessory according to this disclosure. Insome embodiments, an optical device can include one or more mirrors (orother features, such as other reflecting surfaces, for changing the pathof light rays) as well as a mask (or other feature) to help create aparticular pattern of light on a relevant target. As illustrated in FIG.44A, for example, an optical device 500 according to some embodiments ofthe invention includes a pair of mirrors 502 and 504 arranged to directlight from a light source 506 generally along an offset optical axis508. In order to provide a pattern on a relevant target, a mask can beprovided, such as a generally non-reflective mask 510 disposed on themirror 504. In the embodiment illustrated in FIG. 44B, the mask 510includes four oval (e.g. elliptical or circular) openings 512, such thatonly light from the light source 506 that is incident on the openings512 can pass through the mask 510 to be reflected from the mirror 504.Correspondingly, when light from the optical device 500 reaches a target514 it will form a pattern of ovals (e.g., including the ovals 516 and518), as may be useful to help a user align a camera with a barcode.

In the embodiment illustrated in FIG. 44A, the mirrors 502 and 504 aregenerally planar mirrors. In some embodiments, non-planar mirrors can beused. As illustrated in FIG. 45, for example, an optical device 530 isconfigured similarly to the optical device 500, with a pair of mirrors532 and 534 arranged to direct light from a light source 536, throughthe optical device 530, to a target 538. Similarly to the mask 510 (seeFIG. 44A), a mask 540 is provided on the mirror 534 in order to helpproject a pattern of ovals (e.g., as represented by the ovals 542 and544) onto the target 538. In contrast to the optical device 500,however, the mirror 532 of the optical device 530 is configured asparabolic mirror. As illustrated by relatively light paths 546, forexample, this parabolic configuration of the mirror 532 can help tocollimate light from the light source 536 and thereby produce a patternof smaller and more intensely lit ovals (e.g., including the ovals 542and 544) arranged around an optical axis 548.

In the embodiments illustrated in FIGS. 44A and 45, the masks 510 and540 are disposed on the respective mirrors 504 and 534. In someembodiments, a mask (or other similar feature) can be disposed at otherlocations within an optical device. In the embodiment illustrated inFIG. 46, for example, an optical device 550 is configured similarly tothe optical device 530 (see FIG. 45), with a parabolic mirror 552 and aplanar mirror 554 arranged to direct light from a light source 556,through the optical device 550, to a target 558. In contrast to theoptical device 530, however, the optical device 550 includes a mask 560that is disposed between the mirrors 552 and 554, but is not disposeddirectly on either of the mirrors 552 and 554. As illustrated by thelight paths 562 and by the ovals 564 and 566, this configuration canresult in a similar illumination of the target 558 as can be provided bythe optical device 530 for the target 538 (see FIG. 45).

In some embodiments, other configurations of mirrors (or otherreflecting surfaces) can be used. As illustrated in FIG. 47, forexample, an optical device 570 includes a pair of mirrors 572 and 574,and a mask 576 disposed between the mirrors 572 and 574. The mirror 572is configured with a plurality of (e.g., four) elliptical segments, suchas elliptical segments 572 a and 572 b, which can result in light from alight source 578 being divided for travel through a mask 576 alongmultiple optical axes (e.g., optical axes 592 a and 592 b). In theembodiment illustrated, each of the elliptical segments of the mirror572 (e.g., including the elliptical segments 572 a and 572 b) isconfigured and arranged such the respective focal points of ellipsesdefined by the elliptical segments (e.g., ellipses 586 a and 586 bdefined by the segments 572 a and 572 b) are generally coincident withthe light source 578 and with at least one respective opening in themask 576. In the embodiment illustrated, the optical device 570 furtherincludes a set of lenses (e.g., including the lenses 588 and 590)disposed between the mask 576 and the mirror 574, to collimate the lightthat passes through the mask 576. With this configuration, for example,light from the light source 578 can be projected onto a target 580 witha relatively bright and focused pattern (e.g., as represented by theovals 582 and 584).

In some embodiments, an optical device can use features or componentsother than mirrors to direct light. As illustrated in FIG. 48A, forexample, an optical device 600 is configured similarly to the opticaldevice 530 (see FIG. 45), in order to project a pattern (e.g., a patternincluding ovals 602 and 604) on a target 606. In contrast to the opticaldevice 530, however, the optical device 600 includes a transparent body608 with reflecting surfaces 610 and 612 that serve to redirect lightfrom a light source 614, along an optical axis 616, to the target 606.In the embodiment illustrated, the reflective surface 610 is generallyplanar, and the reflecting surface 612 is generally parabolic in orderto collimate light from the light source 614. Further, rather than (orin addition to) the optical device 600 including a mask, the reflectingsurface 612 is configured with four ovular reflective spots 618 (seeFIG. 48B) surrounded by non- (or less) reflective material, in order toreflect light onto the target 606 with a particular pattern (e.g., asrepresented by the ovals 602 and 604).

In other embodiments, other configurations are possible. As illustratedin FIG. 49, for example, an optical device 620 is generally configuredsimilarly to the optical device 600, with a transparent body 622 withreflecting surfaces 624 and 626 to direct light from a light source 628onto a target 630 with a particular pattern (e.g., as represented by theovals 632 and 634) onto the target 630. In the optical device 620,however, the reflecting surface 624 nearest to the light source 628 isconfigured as a generally planar reflecting surface (e.g., rather than aparabolic reflecting surface). Correspondingly, the optical device 620includes a lens 636 disposed between the light source 628 and thereflecting surface 624, in order to collimate light from the lightsource 628 for passage through the transparent body 622 and projectiononto the target 630.

In some embodiments, an attachment for a mobile device can includeelectronic components, such as light sources, processor assemblies(e.g., flexible printed circuit board “PCB” assemblies), sensors, and soon. For example, an optical attachment can include a power source, acontroller such as a PCB assembly with one or more processors, and anLED (or LEDs) that is powered via the power source and controlled by thecontroller. With the assistance of appropriate optical devices of theattachment (e.g., lens assemblies, mirrors, and so on), the LED canprovide light to project an illuminated targeting (or other) patternonto a target for image acquisition. Accordingly, lighting of a targetwith the optical attachment (e.g., for image targeting) can be freedfrom any limitations imposed by a light source on a particular mobiledevice (e.g., limitations regarding pattern color or brightness).Further, with a self-contained power source such as a battery, theoptical attachment can operate at a relatively high power level withoutdraining the battery of the mobile device.

In one embodiment, an attachment can include an attachment body that isremovably securable to a mobile device. The attachment body cangenerally provide a relatively light-proof cover for a camera of themobile device, aside from one or more imaging openings in the attachmentbody, through which the camera can image external targets. Further, theattachment body can house a battery pack and a relatively high-power LEDthat can be operated by an onboard (or remote) processor. An opticaldevice (e.g., a lens arrangement) included in the attachment body can beconfigured to project light from the LED towards external targets, ascan be useful, for example, for targeting operations. In some cases, theoptical device can include a dichroic mirror assembly, which can allowthe LED light to be projected onto the target along the optical axis ofthe camera without requiring the LED to be disposed along the opticalaxis of the camera. For example, in some embodiments, a dichroic mirrorcan be disposed in optical alignment with the camera and with the LED,between two imaging openings in the attachment body. Light for imagingcan accordingly pass from external targets through the imaging openingsand the mirror to reach the camera, while light from the LED can bereflected from the mirror onto the external targets for illumination andtargeting.

In some embodiments, an attachment can be configured to optically (orotherwise) communicate with a mobile device when secured to the mobiledevice for operation. This can be useful, for example, where theoperation of a light source included in an attachment needs to becoordinated with one or more operations on an associated mobile device(e.g., image acquisitions). For example, an attachment can include alight detector (i.e., a photon detector of various kinds) that can bedisposed in optical alignment with a light source on a mobile devicewhen the attachment is secured to the mobile device. With thisarrangement, data can be transmitted from the mobile device to theattachment by projecting light from the mobile-device light source ontothe light detector of the attachment. The attachment can then interpretsignals from light detector to extract the data (e.g., via firmwareapplications, hardware, and so on). As such, for example, softwareoperating on the mobile device can control operation of an attachmentlight source (or other attachment component) in order to projecttargeting patterns for image acquisition (or provide otherfunctionality). Further, in some implementations, software operating onthe mobile device can optically transmit firmware (and other) updates toan attachment so that operation of the attachment can be easily improvedwhen appropriate.

Similarly, in some embodiments, data can be optically (or otherwise)transmitted from an attachment to a mobile device. For example, anattachment can include a light source that can be placed into opticalalignment with a camera of a mobile device, when the attachment issecured to the mobile device. With this configuration, light from theattachment light source can be projected onto the camera in order totransmit data from the attachment to the mobile device (e.g., viainterpretation of the optical signals via software on the mobiledevice). As such, for example, the attachment can optically communicateidentification information, firmware information, and other data to themobile device.

In some implementations, an attachment can communicate certaininformation upon being secured to, or paired with, a mobile device. Forexample, an attachment can be configured to communicate a part number, aserial number, and a firmware version upon first receiving a pairing orcontrol signal from a mobile device, or upon being physically connectedto the mobile device. This can trigger further communication, asappropriate, to complete a connection or pairing of the attachment andthe mobile device, and can thereby enable control of an attachment lightsource by the mobile device.

In some implementations, other data can also be communicated. Forexample, a battery monitor on an attachment can monitor an attachmentbattery (or other power source), so that an attached mobile device canbe provided with status information for the battery (or other powersource). For example, a battery monitor can monitor power status of anon-board battery, then use optical communication to alert a user, viathe mobile device, when the battery is in need of replacement orrecharging.

In some embodiments, an attachment light source for opticalcommunication with a mobile device can also be used to project patternsfor image targeting. For example, the light source can be controlled tocommunicate data via modulation (e.g., controlled ON-OFF flickering) ofa targeting pattern projected onto an external target. By imaging theexternal target, a camera of the mobile device can accordingly recordthe optical data transmission. In contrast, in some arrangements, anattachment light source can be disposed to directly project light ontothe camera (i.e., project light onto the camera without the light beingfirst projected onto an external imaging target). For example, anattachment can include a dedicated (or shared) communication openingthat is optically aligned with the attachment light source and with thecamera, so that light from the LED can be projected onto the camera viathe opening rather than (or in addition to) being projected onto anexternal target.

In some embodiments, an attachment can include a dedicated light sourcefor optical communication as well as one or more additional lightsources. For example, an attachment body can include a first LED forprojecting patterns for image targeting, and a second LED fortransmitting information directly to a camera of an attached mobiledevice.

Although beneficial results can be obtained with non-opticalcommunication, optical communication of data between an attachment and amobile device can have particular advantages. For example, in someembodiments, optical signaling by an attachment can be implemented usingcomponents that are also useful for other purposes (e.g., light sourcesfor projecting targeting patterns onto external targets). Accordingly,communication between an attachment and an associated mobile device canbe obtained without adding expensive and/or sizable electroniccomponents such as Bluetooth equipment, radio antennas, and so on.Similarly, in some embodiments, optical signaling can be implementedwithout necessarily requiring a user to secure and maintain of externaldata connections. For example, communication architectures relying onhead-phone or other data-port connections can require plugs or cordsthat extend well outside of an attachment, and are thus potentiallysubject to accidental disconnect or damage, as well as other issues.

An example aimer accessory 700, which includes some of the features andcapabilities discussed above, is illustrated in FIG. 50 as secured to amobile device case 702. Generally, the aimer accessory 700 includes anattachment body 704 and an attachment base (not shown in FIG. 50) thatis configured to removably secure the attachment body 704 to the case702. The attachment body 704 includes a shell 706, which is generallycontoured to compliment the geometry of the case 702 and which includesa main optical opening 708 with a cover lens 710. When the aimeraccessory 700 is attached to the case 702, and a mobile device (notshown in FIG. 50) is placed within the case, a camera of the mobiledevice can be aligned to acquire images through the optical opening 708.In some embodiments, as also discussed below, light from an internallight source (not shown in FIG. 50) can also pass through the opticalopening 708, in order to project a targeting pattern for imageacquisition with the camera.

In some embodiments, the aimer accessory 700 can be removably secured tothe case 702 (e.g., for targeting and image acquisition operations)using an attachment base configured to removably engage the attachmentbody 704. An example attachment base 716, formed as a single integralbody, is illustrated in FIGS. 51A and 51B.

The attachment base 716 is generally configured to engage with the case702 at an imaging opening in the case 702 (not shown in FIGS. 51A and51B). To that end, for example, the attachment base 716 includes ananchor portion 716 a with a relatively large optical (e.g., imaging orcamera) opening 718. The optical opening 718 is generally configured sothat a camera of a mobile device within the case 702 can acquire imagesthrough the image opening when the attachment base is secured to thecase 702. Surrounding the optical opening 718, the anchor portion 716 aincludes a sidewall with an exterior shoulder 720.

In some embodiments, when the attachment base 716 is installed in thecase 702 with a mobile device, the underside of an attachment base canrest against parts of the mobile device. Accordingly, in someembodiments, the attachment base 716 can be contoured to match thegeometry of a particular mobile device type. For example, the undersideof the anchor portion 716 a (see FIG. 51B) of the attachment base 716includes a generally flat portion 722 a and a curved portion 722 b,which are generally contoured to match the geometry of a phone for usewith the case 702. In other embodiments, other configurations arepossible.

The attachment base 716 also includes a generally plate-like tongue 724,attached to and extending away from one end of the anchor portion 716 a.The tongue 724 attaches to the anchor portion 716 a at a pair of raisedshoulders 726 and extends from the shoulders 726 to a rounded end 728.The tongue 724 is generally resiliently deformable, with a central,partially spherical recess 730 at the rounded end 728. An exteriorshoulder 732 extends around the outer perimeter of the tongue 724,facing generally oppositely from the shoulder 720 to form a pair ofparallel attachment rails between the shoulders 726 and the rounded end728.

As illustrated in FIG. 52A, to secure an attachment body (e.g., theattachment body 704) to the case 702, the attachment base 716 isgenerally disposed in an optical opening 734 in the case 702. Inparticular, the shoulder 720 (see FIGS. 51A and 51B) can be disposed tothe inside of a shoulder 736 surrounding the optical opening 734 in thecase 702. With the shoulder 720 thus disposed, the attachment base 716(e.g., at the portions 722 a and 722 b illustrated in FIG. 51B) sitsrelatively flushly with the interior of the case 702. Further, theattachment base 716 extends partly through the optical opening 734 ofthe case 702 so that the tongue 724 extends partly along the exterior ofthe case 702, adjacent to the optical opening 734. With a mobile device(e.g., a mobile phone) disposed within the case 702, the mobile deviceand the shoulders 720, 736 can accordingly hold the attachment base 716firmly in place and in optical alignment with the optical opening 734.In this way, for example, the attachment base 716 can be disposed tosecure an attachment body to the case 702, while still allowing usefuloperation of a camera 738 and a light source 740 of a mobile device 742via the optical opening 718.

Generally, the use of a separate attachment base (e.g., the attachmentbase 716) can allow for relatively easy addition or removal of an aimeraccessory for a particular mobile device. This can be particularlyuseful, for example, in self-powered versions of aimer accessories, forwhich it may be useful to rapidly swap a fully-charged accessory for anaccessory with a depleted internal power source. Similarly, the use of aseparate attachment base can also allow for a relatively modular rangeof different aimer accessories. For example, multiple attachment bodies,each with different optical arrangements (or other components), can beconfigured to universally attach to a particular attachment base,thereby allowing one of several attachment bodies to be selected for aparticular task with a particular mobile device.

FIGS. 53A and 53B illustrate an example base plate 750, formed as anintegral molding, for use to attach an attachment body (e.g., theattachment body 704) to an attachment base (e.g., the attachment base716). As illustrated in FIG. 53B in particular, the base plate 750includes a recess 752 extending into the attachment base 716 to an endwall 752 a. A set of rails 754 on opposite sides of the recess 752generally define parallel grooves 756, and a cut-out 758 defines alocking finger 760 with a central boss 762 having generallycomplimentary geometry to the recess 730 on the tongue 724 of theattachment base 716 (see, e.g., FIG. 51A). Accordingly, as alsodiscussed below, the recess 752 can generally receive the tongue 724 tosecure the attachment base 716 to the base plate 750, with the railsformed by the shoulder 732 of the tongue 724 (see, e.g., FIG. 51A) beingslidingly received within the grooves 756. Further, with the shoulder732 fully received within the grooves 756 and with the shoulders 726 onthe attachment base 716 urged against the end wall 752 a of the recess752 (see, e.g., FIG. 56), the boss 762 can snap into the recess 730(see, e.g., FIG. 51A) to lock the base plate 750 in place relative tothe attachment base 716.

Also illustrated in FIG. 53B, the base plate 750 can include otherfeatures to help align and secure the base plate 750 for attachment tothe attachment base 716 and the case 702. For example, in the embodimentillustrated, a pair of rounded guides 764 extends outward from thebottom side of the base plate 750, as may be useful for aligning andengaging the base plate 750 with the attachment base 716. Similarly, thebottom side of base plate 750 includes a generally planar flat borderportion 766 a and a curved border portion 766 b. In some embodiments,the flat and curved border portions 766 a, 766 b (or other portions ofthe bottom of a base plate) can be configured to be generallycomplimentary to the geometry of a particular case (e.g., the case 702).

To support and secure different components of the aimer accessory 700(e.g., one or more optical devices) relative to the base plate 750, thetop side of the base plate 750 includes a number of support andengagement features. As illustrated in particular in FIG. 53A, forexample, a set of hooks 768, a number of posts 770, 772, 774, and a pairof support wedges 776 can be integrally formed with (or otherwiseconnected to) the base plate 750. In some embodiments, features such asa curved containment wall 778 can serve to wholly or partly subdividethe interior of the attachment body 704 into different compartments. Forexample, in combination with the shell 706 (see FIG. 1) and a batterydoor 780 (see FIG. 54), the containment wall 778 can form an on-boardbattery compartment for the aimer accessory 700.

Other portions of a base plate for an attachment body can also includeuseful features. For example, each of the lateral sides of the baseplate 750 includes a set of wedged protrusions 786 that can help tosecure the shell 706 (see, e.g., FIG. 1) to the base plate 750. In someembodiments, the protrusions 786 can be configured for relatively securesnap-engagement with corresponding features on the interior of the shell706.

As also discussed above, it may be useful to capture images throughoptical openings in an aimer accessory, as well as to exchange opticalcommunication signals with an attached mobile device. To this end, forexample, the base plate 750 includes a pair of optical openings 782,784. In the example configuration discussed below, the opening 782 isconfigured as an imaging opening and the opening 784 is configured as acommunication opening for transmission of optical communications.Communication and imaging via the openings 782, 784 is also discussedbelow.

In other embodiments, other configurations are possible. In someembodiments, a base plate can include a different number or arrangementof optical openings. For example, a base plate for use with the aimeraccessory 700 can include multiple optical openings for transmission ofoptical communication (i.e., multiple communication openings), or caninclude only a single optical opening for both communicationtransmissions and imaging.

In some embodiments, a bottom portion of a base plate can be configuredto engage with any variety of attachment bases, or to match the geometryof any variety of mobile-device cases. In some embodiments, alternative(or additional) locking devices can be used. For example, the boss 762of the base plate 750 can be instead configured as a recess sized toengage a corresponding protrusion on an associated attachment base.

As illustrated in FIG. 55, with the shell 706 attached to the base plate750, the attachment body 704 can be positioned next to the case 702, inlateral alignment with the attachment base 716 (see, e.g., FIG. 52B).The attachment body 704 can then be slid, as indicated by arrow 788,into the attached configuration of FIGS. 56 and 57. The case 702 and themobile device 742 are not illustrated in FIG. 56 to better show certainfeatures of the assembled attachment body 704 and attachment base 716.

As illustrated in particular in FIG. 56, the battery door 780 includes arecess 790 that is generally complimentary to the rounded end 728 of thetongue 724 of the attachment base 716. Further, with the battery door780 snap-engaged (or otherwise secured) to the base plate 750, therecess 790 on the battery door 780 is generally aligned with the recess752 in the base plate 750. Accordingly, during installation of theattachment body 704 onto the case 702, the tongue 724 can be alignedwith and seated within the recess 790 in order to dispose the shoulder732 of the tongue 724 for sliding engagement with the grooves 756 of thebase plate 750.

As also illustrated in FIG. 56, with the base plate 750 secured to theattachment base 716, the guides 764 on the base plate 750 are disposedagainst opposite internal walls of the optical opening 718 in theattachment base 716. This can assist in proper alignment of theattachment base 716 during installation, as well as provide additionalstability for the attachment base 716 once it is secured in place.

Further, with the base plate 750 secured to the attachment base 716, theimaging opening 782 and the communication opening 784 of the base plate750 are disposed generally within the optical opening 718 of theattachment base 716. Accordingly, for example, light source 740 of themobile device 742 (see, e.g., FIG. 52B) can provide optical signalsthrough the communication opening 784, and the camera 738 of the mobiledevice 742 both can capture images through the imaging opening 782 andreceive optical signals through the communication opening 784. In otherembodiments, optical openings on an attachment base (e.g., the imagingopening 782 and the communication opening 784) can be otherwiseoptically aligned with an optical opening of an attachment base (e.g.,disposed along a shared optical axis with, but not within, theattachment-base optical opening).

As illustrated in particular in FIGS. 54 and 57, the battery door 780includes a rounded ridge 792 at one end. The ridge 792 can be configuredto engage (e.g., snap-engage) with a corresponding recess 794 on theinterior of the shell 706, in order to further secure the case 702 tothe base plate 750.

FIGS. 56 and 57 illustrate certain structural aspects of the assembly ofthe shell 706, the base plate 750, and the attachment base 716, but donot illustrate a particular set of components that can be housed by theshell 706 and the attachment body 704 generally. Depending on thedesired use of the aimer accessory 700, different optical devices andother components, and different arrangements thereof, can be disposedwithin the attachment body 704. In some embodiments, the aimer accessory700 may include components that do not necessarily relate to aiming (ortargeting) operations.

An example set of components for the aimer accessory 700 is illustratedin FIGS. 58 and 59. Generally, in the embodiment illustrated, theattachment body 704 is configured to include a dichroic mirror 810, aPCB assembly 812 (e.g., multiple PCBs 812 a, 812 b, 812 c, connected byribbon cables), a battery pack 814 to power the PCB assembly 812, and anoptical assembly supported by an optics block 816. The PCB assembly 812can be mounted to the posts 772, 774, at the PCB 812 b, as well as tomounting posts 818 on the optics block 816, at the PCB 812 c (see FIG.59, only one of the posts 818 shown). In turn, the optics block 816 canbe secured to the base plate 750 using the posts 770 (see FIG. 53A) andthe hooks 768. The battery pack 814 can be contained by the containmentwall 778 and the battery door 780. The dichroic mirror 810 can besecured in place in optical alignment with the imaging opening 782 byboth the support wedge 776 of the base plate 750 and a set of grooves820 within the shell 706.

As illustrated in FIG. 59 in particular, the optics block 816 isconfigured to support a lens 822 so that a primary optical axis of thelens 822 is aligned at an angle (e.g., 45 degrees) relative to thedichroic mirror 810. Further, the optics block 816 includes a fixedconical aperture 824 and a light-source recess 826. In the embodimentillustrated, the PCB 812 c of the PCB assembly 812, which supports anLED 828 (e.g., a green LED), is supported by the mounting posts 818 sothat the LED 828 is disposed within the light-source recess 826 ingeneral alignment with the conical aperture 824. Accordingly, when theLED 828 is activated (e.g., as powered by the battery pack 814 andcontrolled by the PCB assembly 812), light from the LED 828 can beprojected through the conical aperture 824 and the lens 822 onto thedichroic mirror 810, to be reflected out the optical opening 708 of theshell 706 and onto a target (not shown). This is illustrated in FIG. 59with an example optical path 832, and can be generally useful forgeneral target illumination as well as for projecting targetingpatterns.

Because of the optical properties of the dichroic mirror 810, light fromthe target that reflects back to the aimer accessory 700 and passesthrough the optical opening 708 can be received by the camera 738 forimaging via the dichroic mirror 810, the optical opening 734, and theimaging opening 782. This is illustrated in FIG. 59 with an exampleoptical path 834. Of note, light from the LED 828 that travels along theoutbound optical path 832 can be reflected from the target into theinbound optical path 834 for imaging by the camera 738.

As also illustrated in FIG. 59 in particular, a part 812 a of the PCBassembly 812 is disposed over the communication opening 784 of the baseplate 750. Accordingly, a light detector 830 supported by the part 812 aof the PCB assembly 812 is disposed to directly receive optical signalsfrom the light sources 740 of the camera. In the embodiment illustrated,the part 812 a of the PCB assembly 812 fully occludes the communicationopening 784, so that light from the LED 828 generally cannot passdirectly from the aimer accessory 700, through the communication opening784, to the camera 738. In other embodiments, other configurations arepossible, including configurations in which light from the LED 828 ispermitted to pass through the communication opening 784.

In some embodiments, an optical arrangement for an aimer accessory caninclude other types of reflectors or filters in place of (or in additionto) a dichroic mirror such as the dichroic mirror 810. Likewise, in someembodiments, the part 812 a of the PCB assembly 812 (or another feature)can support a light source distinct from the LED 828 for directcommunication with the mobile device 742 via the communication opening784 and the camera 738. In some embodiments, as also noted above,optical devices (or general structural arrangements) can be included todirect light from the LED 828 through the communication opening 784 fordirect communication with the mobile device 742.

In some embodiments, one or more filters or masks (not shown) can beincluded. For example, filters or masks can be included to allow the LED828 to provide an aiming pattern generally similar to those discussedabove, or various other aiming patterns.

In some embodiments, other power sources can be provided. For example, alarger battery compartment and battery pack can be included, or an aimeraccessory can draw power from an external (e.g., separate but attached)battery pack.

In some embodiments, the configuration of the optics block 816 and therelative arrangement of the optics block 816 and the LED 828 (or otherlight source) can be used to obtain a particular type of illuminationpattern with the LED 828. As illustrated in FIGS. 60A through 60D, forexample, placement of the LED 828 in a first location 840 can provide asomewhat large and relatively diffuse illumination pattern 842 on atarget. If the LED 828 is moved away from the conical aperture 824 to asecond location 844, a somewhat smaller and relatively more focusedillumination pattern 846 can be provided on the target. If the LED 828is moved still farther away from the conical aperture 824 to a thirdlocation 848, a still smaller and more intense illumination pattern 850can be provided on the target. Accordingly, a particular location forthe LED 828 relative to the optics block 816 can be chosen depending onthe desired characteristics of an illumination pattern.

An example control architecture for the PCB assembly 812 is illustratedin FIG. 61. In the embodiment illustrated, the battery pack 814 isarranged to power a low-dropout (“LDO”) regulator 856, the lightdetector 830 (e.g. configured as a photo transistor), and a dedicatedcontroller 858 for the LED 828. A microcontroller 860 powered by the LDOregulator 856 is configured to exchange data, including commands, withthe light detector 830 and the LED controller 858. Accordingly, themicrocontroller 860 can generally control characteristics (e.g., timing,duration, and intensity) of lighting from the LED 828, including basedupon optical signals received at the light detector 830.

In other embodiments, other configurations are possible. For example, anadditional LED and an additional LED controller (not shown) can bedisposed in communication with the microcontroller 860, or with anotherprocessing device. This can be useful, for example, in order to providea dedicated light source for optical communication with an associatedmobile device. Likewise, in some embodiments, other electronic devicescan additionally (or alternatively) be included.

Another example aimer accessory 880 is illustrated in FIGS. 62 through64. In various aspects the aimer accessory 880 is similar to the aimeraccessory 700. In other aspects, however, some of which are detailedbelow, the aimer accessory 880 differs from the aimer accessory 700.

Similarly to the aimer accessory 700, the aimer accessory 880 includesan attachment body 882 with an optical opening 882 a, and an attachmentbase 884 (see, e.g., FIGS. 63A and 63B). As illustrated in FIGS. 63Athrough 64, the attachment base 884 includes a exterior shoulder 886 toengage a corresponding interior shoulder 888 in an optical opening 890of a case 892 for a mobile device 894. The attachment base 884 alsoincludes a tongue 896 that is disposed outside of the case 892, toengage the attachment body 882, when the attachment base 884 isinstalled for use (see, e.g., FIG. 64).

The attachment body 882 includes a base plate 898 configured to engage ashell 906, to generally support optical devices and other components,and to slidingly engage the attachment base 884 to secure the attachmentbody 882 to the mobile-device case 892. Similarly to the base plate 750,the base plate 898 includes a locking finger 900 with a boss 902configured to engage a corresponding recess 904 on the tongue 896 of theattachment base 884. The base plate 898 also includes a pair of curvedguides 908 disposed to engage the interior sides of an optical opening910 in the attachment base 884.

The base plate 898 further includes an imaging opening 912 and acommunication opening 914, which are optically aligned with the opticalopenings 890, 910, when the base plate 898 is installed for use (see,e.g., FIG. 64). In contrast to the base plate 750, the communicationopening 914 is somewhat larger than the communication opening 784. Thiscan be useful, for example, if a light detector and a light source (orother devices) are each to be disposed for optical communication throughthe communication opening 914.

Support structures on the top of the base plate 898, as well as theoptical devices housed by the shell 906, also vary from those of thebase plate 750 and the shell 706. For example, as illustrated in FIG.63B in particular, the base plate 898 includes an angled recess 920 withan elongate support ramp 922. The recess 920 and the support ramp 922receive and support an optics block configured as an open chassis 924,which in turn supports a dichroic mirror 926, and a PCB assembly 928.Generally, the PCB assembly 928 includes an LED (not shown) that can bedisposed in a light-source recess 930 of the chassis 924. In someembodiments, a communication block 932 can also be included.

With the chassis 924 installed on the base plate 898 and the base plate898 secured to the attachment base 884, the dichroic mirror 926 isoptically aligned with the imaging opening 912 on the base plate 898.Accordingly, the aimer accessory 880 can be used similarly to the aimeraccessory 700, in order to project an aimer pattern onto an externaltarget (not shown), while also providing an optical path for a camera934 of the mobile device 894 to image the target. Further, with theaimer accessory 880 appropriately installed, the communication opening914 and the communications block 932 are optically aligned with theoptical opening 910 on the attachment base 884. Accordingly, via thecommunications block 932, the camera 934 and a mobile-device lightsource 936, the aimer accessory 880 can directly optically communicatewith the mobile device 894.

In other embodiments, other configurations are possible. In someembodiments, for example, the communications block 932 can be astructural block or other member, rather than part of a PCB assembly. Assuch, for example, with the various components of the aimer accessory880 arranged as illustrated in FIG. 64, the communications block 932 canfully occlude the communication opening 914 so that opticalcommunication through the communication opening 914 is prevented. Theaimer accessory 880 can accordingly, for example, optically communicatewith the mobile device 894 by projecting a modulated illuminationpattern onto an external target (i.e., via the optical opening 882 a)for imaging by the camera 934.

In some embodiments, masks, filters, or other similar devices can beincluded. In the embodiment illustrated, for example, a pinhole mask 938is disposed between the light-source recess 930 and a lens 940, in orderto provide for projection of an appropriate pattern of light from theLED (not shown) onto an external target.

In the embodiment of FIGS. 62 through 64, the PCB assembly 928 is notfully illustrated, in order to better show certain other aspects of theaimer accessory 880. A variety of PCB configurations, including thosesimilar to the PCB assembly 812, can be used in order to provide theaimer accessory 880 with appropriate capabilities. Likewise, although abattery pack or other power source is not directly illustrated in FIGS.62 through 64, the aimer accessory 880 can be configured to draw powerfrom a variety of power sources, such as onboard or external batterypacks (not shown).

Optical communication between an aimer accessory and a mobile device canbe effected in various ways. Generally, for example, it may be useful totransmit data via binary signaling, with modulation of mobile-device andattachment light sources providing bit information, and with one or morecontrollers implementing appropriate packet architecture, forward errorcorrection, signal decoding, and so on.

In some embodiments, a mobile device can be configured to capture video,or a series of still-frame images, then analyze the resulting image datato identify optical signals. For example, a camera of a mobile devicecan capture video of a target on which a projected targeting pattern isbeing modulated, and can then analyze the video to identify abinary-encoded signal from the modulation. In some implementations, thevideo (or a similar series of still images) can be converted tograyscale and then adjusted to a relatively high level of contrast. Theresulting high contrast images can then be compared to a reference image(e.g., a previously-acquired reference image of an illuminated, ornon-illuminated, target) to determine the nature of the imaged data(e.g., an illuminated “1”, or a non-illuminated “0”). As appropriate,once a certain amount of information has been thus received and/ordecoded, a check (e.g., cyclic redundancy check (“CDC”) error detecting)can be executed to determine whether the information represents a validcommunication signal.

In some embodiments, a light source of a mobile device can be used toestablish a timing for optical transmission of data from an aimeraccessory to the mobile device. For example, the light source of themobile device can be cycled on and off rapidly, with a predetermined(e.g., hardware-limited minimum) interval between successive “on”states. Over the interval between the “on” states, the mobile device cancapture images of a relevant illumination target (e.g., an imagingtarget being illuminated by a light source of the aimer accessory).Depending on whether an image that is captured during the intervalindicates an “on” state for the light source of the aimer accessory, themobile device can then register a bit of one type (e.g., a “1”) oranother (e.g., a “0”). In this way, for example, with appropriatemessage validation and error correction, relatively reliable opticalcommunication from the aimer accessory to the mobile device can beobtained. The approach noted above, and others like it, may be useful,for example, in embodiments in which the mobile device and the aimeraccessory lack a common clock or other timing synchronization.

In some embodiments, a somewhat reversed implementation mayalternatively (or additionally) be possible. For example, an aimeraccessory can be configured to transmit an “intro” or “prefix” message,a timing message, or other optical message to a mobile device in orderto initiate and/or regulate timing for a transmission of optical datafrom the aimer accessory to the mobile device.

In some implementations, a mobile device can be configured tocommunicate with an aimer accessory in a relatively direct fashion. Forexample, when the aimer accessory is set to receive data (e.g., as adefault configuration of the aimer accessory) the light source of themobile device can be modulated (e.g., switched controllably on and off)in order to selectively trigger a light detector of the aimer accessory.An associated controller can receive the trigger signals from the lightdetector, and can then decode, verify, and act on the signals asappropriate (e.g., to command illumination of a targeting pattern inresponse to a request from the mobile device).

As also noted above, optical communication between a mobile device andan aimer accessory can be useful in implementing a variety of functions.For example, a mobile device can optically communicate with an aimeraccessory to trigger illumination of a target with a targeting pattern.In some implementations, the mobile device can further provide, orotherwise cause an aimer accessory to select and implement, one or moreparameters for the illumination, such as light color, timing, intensity,duration, pattern, modulation type (e.g., steady illumination orflashing illumination) and so on. As another example, a mobile devicecan communicate firmware updates or other useful information to an aimeraccessory (e.g., identification information for the mobile device), sothat the aimer accessory can be operated with appropriate efficiency andfunctionality.

In some implementations, an aimer accessory can optically communicatewith a mobile device in order to provide information regarding the aimeraccessory. For example, when first attached to or paired with a mobiledevice, or at other times, an aimer accessory can optically communicateidentifying information, such as part and serial numbers, and firmwareversion. Software on the mobile device can then respond appropriately,including by registering the aimer accessory (e.g. locally with themobile device, or remotely with a registration server), enabling ordisabling particular options for controlling the aimer accessory,automatically opening menus or other interfaces, automatically providinga firmware update or reminder to update firmware, and so on. Similarly,an aimer accessory can communicate other information, including alertswith regard to battery life or other factors pertinent to accessoryperformance.

Battery monitoring to inform alerts relating to battery life can beimplemented in various ways. In some implementations, for example, theaimer accessory (or a mobile device) can track how often an LED of theaimer accessory is on. Because operation of an LED can represent asignificant portion of power expenditure, total operation time for anLED can serve as (or help to determine) a relatively accurate indicatorof battery life for an aimer accessory. In some implementations, abattery monitor can simply detect brown-outs or delays at a relevantcontroller and can infer a particular battery state from a particularfrequency or severity of these events. In some implementations, ratherthan (or in addition to) communicating battery information to a mobiledevice, an aimer accessory can include an external battery-lifeindicator (e.g., an external LED). In some implementations, informationrelating to battery life can be stored in memory within an aimeraccessory, so that appropriately accurate battery-life information canbe determined despite changes between different mobile devices orrelatively long delays between use of the aimer accessory.

Consistent with the discussion above, some embodiments of the inventioncan include a communication and control method 950 as illustrated inFIG. 65. As illustrated in FIG. 65, the spatial order of operations doesnot necessarily correlate with the temporal order of the operationsduring implementation of the method 950. Likewise, connections betweenoperations as illustrated in FIG. 65 (e.g., as may indicate flow of databetween software modules) are provided by way of example only. In someimplementations, the various illustrated operations (or others) can beinterconnected and can otherwise interoperate in various ways.

Generally, under the method 950, first optical signals can be received952 at a light detector of an attachment for a mobile device. In someimplementations, the first optical signals can be transmitted 954 to theattachment by a light source of the mobile device. The transmitted 954first optical signals can include various information, includinginstructions for initialization or operation of the attachment. In someimplementations, for example, based on receiving the first opticalsignals, a processing device can activate 956 a at least one lightsource of the attachment for use in image acquisition or targeting(e.g., projection of an illuminated target pattern). In someimplementations, based on receiving the first optical signals, aprocessing device can undertake other operations. For example, theprocessing device can select and implement 956 b particular operational(e.g., illumination) parameters for the attachment, configure theattachment for communication with the particular mobile device, and soon.

Also under the method 950, the processing device can activate 958 the atleast one light source of the attachment in order to provide secondoptical signals to the imaging device. In this way, for example,non-image information 960 such as identification information for theattachment, firmware information for the attachment, power-source statusfor the attachment, information regarding illumination or otherparameters for the attachment, and so on, can be transmitted from theattachment to the mobile device.

In some implementations, the attachment can include at least two lightsources. Accordingly, for example, a first light source can be activated956 a for use in image acquisition or targeting, and a second lightsource can be activated 958 to transmit non-image information 960 to themobile device. In this regard, for example, activation 958 of a lightsource for transmission of optical signals to the mobile device canoccur independently of, or in coordination with, activation 956 a of alight source for image acquisition or targeting or various otheroperations.

In some implementations, the non-image information 960 can betransmitted to the mobile device by activating 958 an attachment lightsource to illuminate 962 an external target, then acquiring 964 imagesof the target with the imaging device of the mobile device. In this way,although the imaging device may acquire one or more images of the targetas part of the communication of the non-image information 960, upondecoding the captured images can provide the non-image information 960in non-image form. For example, the illumination 960 can be modulated onand off in order to encode binary data for transmission to the imagingdevice in order to transmit identification information, firmwareinformation, power-source (e.g., battery) status, and so on.

It will be understood that many variations on the embodiments discussedabove may be possible, including variations combining elements ofmultiple of the embodiments together, variations substituting elementsfrom one embodiment for elements of another embodiment, and variationsrearranging elements of one or more embodiments. For example, withregard to the optical devices illustrated in FIGS. 44A through 49 (andothers), it may be possible to include collimating elements (e.g.,parabolic mirrors or reflecting surfaces, lenses, and so on) before amask, after a mask, or both before and after a mask, relative to thepath of light from a light source to a target. Likewise, in someembodiments, one or more masks can be disposed at various locationswithin the relevant optical device than those specifically illustrated,one or more mirrors can be used in combination with one or moretransparent bodies and reflecting surfaces, projection patterns otherthan patterns of ovals can be used, and so on.

There is thus disclosed an aimer module, aimer accessory and method fora mobile device. In some embodiments, the aimer module collimatesdiffuse light from a lamp on a mobile device for use in capturing abarcode image. The aimer module includes a means for receiving lightfrom a lamp of the mobile device, and a means for generating a lightpattern on the surface containing a barcode. The receiving means and thegenerating means may include a grating and/or configuration of mirrors.Registration of the light pattern and the barcode in a scan areaenhances the ability of the specialized software on the mobile device toread the barcode.

In one embodiment, an aimer module for a mobile device is provided. Theaimer module includes a grating configured to receive light from a lampof the mobile device and to generate a light pattern on the surfacecontaining a barcode. Registration of the light pattern and the barcodein a scan area enhances the ability of the specialized software on themobile device to read the barcode.

An optical element for receiving light from the lamp and providing thelight to the grating may be included. The optical element may furtherinclude at least one of a lens, a reflective surface, a light pipe andan optical fiber. A collector may be included that is configured forcollecting light incident upon the camera.

The grating may include at least one of a pair of substantially parallelslits and a substantially rectangular array of holes. The aimeraccessory may be configured to offset light from the lamp away from thecamera, and may be configured to extend an optical range for reading thebarcode. The aimer accessory may be configured as one of a simple offsetaimer, a basic aimer, an elongated offset aimer, a standard offsetaimer, or a tube offset aimer.

The aimer accessory may be configured for reading a barcode including ina format that is one of: Codabar; Code 25 (Interleaved); Code 25(Non-interleaved); Code 11; Code 39; Code 93; Code 128; CPC Binary; DUN14; EAN 2; EAN 5; EAN-8, EAN-13; Facing Identification Mark; GS1-128;GS1 DataBar; HIBC; Intelligent Mail barcode; ITF-14; JAN; KarTrak ACI;Latent image barcode; MSI; Pharmacode; PLANET; Plessey; PostBar;POSTNET; RM4SCC/KIX; Telepen; UPC; as well as others.

The aimer accessory may be configured for reading a barcode including aformat that is one of: Aztec Code; Code 1; ColorCode; Color ConstructCode; CrontoSign; CyberCode; d-touch; DataGlyphs; Data Matrix; DatastripCode; digital paper; EZcode; Color; High Capacity Color Barcode;HueCode; InterCode; MaxiCode; MMCC; NexCode; Nintendo e-Reader; Dotcode;PDF417; QR code; ShotCode; SPARQCode; as well as others.

In another embodiment, a mobile device configured for blind or targetedscanning of a barcode is provided. The mobile device includes an aimermodule affixed to the mobile device. The aimer module includes a gratingconfigured to receive light from a lamp of the mobile device and togenerate a light pattern on the surface containing a barcode.Registration of the light pattern and the barcode either in a scan areailluminated by the aimer module or in the near vicinity of the lightpattern enhances the capability of a camera of the mobile device to readthe barcode.

The mobile device may include one of a smartphone, a tablet computer, orother special purpose device. Blind and targeted scanning may enablereliable readout of the barcode without use of a display. The lightpattern may include parallel lines, a single line, a square orrectangle, an image outline, a single or an array of dots, an arrow, aset of crosshairs, or other shapes or images.

The mobile device may include a computer program product that consistsof machine executable instructions stored on non-transitory machinereadable media, with the instructions configured for performing thefunctions depicted in FIG. 19.

According to a method of this disclosure, light is emitted from a lampof the mobile device along a first optical path toward a barcode target.The first optical path defines a light axis L. The optical path of theemitted light is then changed from the first optical path to a secondoptical path that is oblique to the barcode target. The optical path ofthe emitted light is then changed again from the oblique optical path toa third optical path that is directed at the barcode target. The thirdoptical path defines a light shifted axis L. Finally, the mobile devicecaptures the image of the barcode target.

In some embodiments, an aimer accessory for a mobile device is provided.The aimer accessory includes a body configured for being affixed to themobile device. The body includes a collimator terminating with a gratingdisposed in a distal portion thereof. The grating is configured toreceive light from a lamp of the mobile device and to generate a lightpattern on the surface containing a barcode. Registration of the lightpattern and the barcode in a scan area enhances the ability of themobile device to capture a barcode image. Registration may be configuredfor blind mode or target mode scanning. In blind mode scanning, theregistration occurs on a detection of the light pattern and the barcodein a viewing angle of a camera of the mobile device. In target modescanning, the registration occurs on a detection of the light patternhovering over the barcode in a viewing angle of a camera of the mobiledevice.

The accessory may further include an optical element for receiving lightfrom the lamp and providing the light to the grating. The opticalelement may include at least one of a lens, a reflective surface, alight pipe and an optical fiber. The accessory may further include acollector configured for collecting light incident upon the camera. Thegrating may include at least one of a pair of substantially parallelslits and a substantially rectangular array of holes.

The accessory may be configured to offset light from the lamp away fromthe camera. The offset may be configured to extend an optical range forreading the barcode. The accessory may be configured as one of a simpleoffset aimer, a basic aimer, an elongated offset aimer, a standardoffset aimer, a tube offset aimer, and a fitted aimer.

The body of the accessory may further include a retainer for retainingthe accessory on the mobile device. The retainer may terminate in aclip. The accessory may be configured as a clip-on accessory.

The accessory may be configured for reading a barcode including a formatthat is one of: Codabar; Code 25, non-interleaved 2 of 5; Code 25interleaved 2 of 5; Code 11; Code 39; Code 93; Code 128; CPC Binary; DUN14; EAN 2; EAN 5; EAN-8, EAN-13; Facing Identification Mark; GS1-128;GS1 DataBar; HIBC; Intelligent Mail barcode; ITF-14; JAN; KarTrak ACI;Latent image barcode; MSI; Pharmacode; PLANET; Plessey; PostBar;POSTNET; RM4SCC/KIX; Telepen; and, U.P.C.

The accessory may be configured for reading a barcode comprising aformat that is one of: Aztec Code; Code 1; ColorCode; Color ConstructCode; CrontoSign; CyberCode; d-touch; DataGlyphs; DataGlyphs; DataMatrix; Datastrip Code; digital paper; EZcode; High Capacity Color; HighCapacity Color Barcode; HueCode; InterCode; MaxiCode; MMCC; NexCode;Nintendo e-Reader#Dot code; PDF417; Qode; QR code; ShotCode; and,SPARQCode. The accessory may be configured for reading a barcodecomprising a plurality of colors.

In another illustrative embodiment, a mobile device configured foreither blind or targeted scanning of a barcode is provided. The mobiledevice includes a body configured for being clipped onto the mobiledevice. The body includes a collimator terminating with a gratingdisposed in a distal portion thereof. The grating is configured toreceive light from a lamp of the mobile device and to generate a lightpattern on the surface containing the barcode. Registration of the lightpattern and the barcode in a scan area enhances the ability of themobile device to capture a barcode image. Registration may be configuredfor blind mode or target mode scanning. In blind mode scanning, theregistration occurs on a detection of the light pattern and the barcodein a viewing angle of a camera of the mobile device. In target modescanning, the registration occurs on a detection of the light patternhovering over the barcode in a viewing angle of a camera of the mobiledevice.

The mobile device may include one of a smart phone, a tablet computerand a special purpose device.

The either blind or targeted scanning enables reliable readout of thebarcode without use of a display. The light pattern may include at leastone of substantially parallel lines, an array of dots, and a set ofcrosshairs. Combinations of slits and holes may be used. A variety oforientations may be provided, and geometric patterns may be used aswell.

In another illustrative embodiment, a method for configuring a mobiledevice for scanning a barcode is provided. The method includes selectingan aimer accessory for the mobile device. The aimer accessory includes abody configured for being affixed to the mobile device. The bodyincludes a collimator terminating with a grating disposed in a distalportion thereof. The grating is configured to receive light from a lampof the mobile device and to generate a light pattern on the surfacecontaining a barcode. Registration of the light pattern and the barcodein a scan area enhances the ability of the mobile device to capture abarcode image. The aimer accessory is affixed to the mobile device. Themethod may further include detecting the light pattern and the barcodein a viewing angle of a camera of the mobile device and capturing theimage of the barcode target. The method may further include detectingthe light pattern as hovering over the barcode in a viewing angle of acamera of the mobile device and capturing the image of the barcodetarget.

The aimer accessory and the code reader application may be employed on avariety of mobile devices. Generally, it is only required that themobile device include a camera, a lamp, and appropriate components foroperation thereof. Examples of other mobile devices include tabletcomputers, as well as special purpose devices such as handheld unitsused for taking field inventory of assets, a dedicated barcode reader,and other such devices.

The grating may generate a variety of light patterns. For example, a setof dots, a single line, a square or rectangle, and crosshairs may beused. Combinations of slits and holes may be used. A variety oforientations may be provided, and geometric patterns may be used aswell. In some embodiments, the grating is configured with regard for aparticular type, or symbology, of barcode that will be read. Forexample, a substantially rectangular array of holes may be useful forregistration with a substantially rectangular barcode, such as a PDF417barcode.

In addition, a variety of techniques may be employed for barcoderecognition. Use of horizontal bars, parallel lines, dots, crosshairs,and other such aiming patterns may be used to assist with barcoderecognition.

An appropriately equipped aimer accessory may provide forre-concentrating light that would otherwise be dispersed.

Software may be downloaded onto or provided with the mobile device ofthis disclosure that produces a software-produced button on the displayof the mobile device. In addition, initiation or triggering of a scan bythe mobile device may be performed by programmatically re-mapping of oneof the mobile device buttons for such use, or triggered externally usingWi-Fi, NFC, or other technology.

The software may further provide user feedback on “good” or “bad”images, or decode of a symbology, via user prompts such as an audiblesound from the mobile device, a vibration from the mobile device, anactivity on the display, such as blinking of the screen, a color change,a movement of an image displayed, etc. Additionally, the feedback may bewirelessly transmitted to a remote location for action, recording, etc.

The aimer module and accessory of this disclosure may further assist inbattery conservation and power management since images may be capturedmore efficiently according to this disclosure.

In some embodiments, an aimer accessory can be formed to include anattachment base and an attachment body that can be removably secured tothe attachment base. The attachment base can be configured to be securedto a mobile device or case through alignment with a case opening,adhesives, magnets, or other attachment mechanisms. The attachment bodycan include an optical device, such as a mirror arrangement, light pipe,or grating, and can be configured to be removably secured to theattachment base. In this way, for example, the attachment body can beremovably secured to the mobile device or case so that the opticaldevice of the attachment body can be used with a camera or light sourceof the mobile device.

In some embodiments, an attachment for use with a mobile device and acase for the mobile device can include an attachment base and anattachment body that can be removably secured to the attachment base.The attachment body can include an optical device, such as a mirrorarrangement, light pipe, grating, LED or other light source, and so on.The attachment base can include an anchor portion configured to disposedat least partly in an interior portion of the case, and a tongueconfigured to extend away from the anchor portion along an exteriorportion of the case. A controller included in the attachment body cancontrol some functions of a light source included in the attachment bodybased upon optical signals received from a light source of the mobiledevice at a light detector included in the attachment body. The lightsource can be controlled to illuminate an imaging target (e.g., with atargeting pattern) and can be controlled to optically communicate withthe mobile device via an imaging device of the mobile device.

In some embodiments, a method of communication between a mobile deviceand an attachment can include a light source of the mobile devicetransmitting optical signals to a light detector of the attachment. Themethod can also include a light source of the attachment transmittingoptical signals to an imaging device of the mobile device.

Various other components may be included and called upon for providingfor aspects of the teachings herein. For example, additional materials,combinations of materials, and/or omission of materials may be used toprovide for added embodiments that are within the scope of the teachingsherein.

Standards for performance, selection of materials, functionality, andother discretionary aspects are to be determined by a user, designer,manufacturer, or other similarly interested party. Any standardsexpressed herein are merely illustrative and are not limiting of theteachings herein.

When introducing elements of the present invention or the embodiment(s)thereof, the articles “a,” “an,” and “the” are intended to mean, unlessotherwise limited or defined, that there are one or more of theelements. Similarly, the adjective “another,” when used to introduce anelement, is intended to mean one or more elements. The terms“including”, “comprising,” “having” and variations thereof are intendedto be inclusive such that there may be additional elements other thanthe listed elements. Similarly, unless otherwise limited or defined, thephrases “at least one of A, B, and C,” “one or more of A, B, and C,” andthe like, are meant to indicate A, or B, or C, or any combination of A,B, and/or C, including, potentially, single or multiple instances ofeach of A, B, and/or C.

While the invention has been described with reference to illustrativeembodiments, it will be understood by those skilled in the art thatvarious changes may be made and equivalents may be substituted forelements thereof without departing from the scope of the invention. Inaddition, many modifications will be appreciated by those skilled in theart to adapt a particular instrument, situation or material to theteachings of the invention without departing from the essential scopethereof. Therefore, it is intended that the invention not be limited tothe particular embodiment disclosed as the best mode contemplated forcarrying out this invention, but that the invention will include allembodiments falling within the scope of the appended claims.

What is claimed is:
 1. An attachment for use with a mobile device and a case for the mobile device, the mobile device including an imaging device and a mobile-device light source, and the case including a case optical opening that is optically aligned with one or more of the imaging device and the mobile-device light source when the case is secured to the mobile device, the attachment comprising: an attachment base configured to be secured to the case with the attachment base disposed at least partly within the case optical opening wherein the attachment base includes an anchor portion and a tongue extending from the anchor portion; an attachment body configured to be removably secured to the attachment base; the attachment body including at least one optical device for use with the imaging device during image targeting and image acquisition; and the attachment base removably securing the attachment body to the case when the attachment body is secured to the attachment base and the attachment base is secured to the case.
 2. The attachment according to claim 1, wherein, to secure the attachment base to the case, the anchor portion is disposed at least partly in an interior portion of the case, between the case and the mobile device, with the tongue extending away from anchor portion along an exterior portion of the case.
 3. The attachment according to claim 2, wherein, when the attachment base is secured to the case: an optical path for image acquisition of an external target by the imaging device extends from the imaging device through the attachment base and the attachment body to the external target; and an optical path for illumination extends between the at least one optical device of the attachment body and at least one of the imaging device and the mobile-device light source.
 4. The attachment according to claim 2, with the case including a case shoulder that at least partly surrounds the case optical opening, wherein the attachment base includes a base shoulder that at least partly surrounds a base optical opening; and wherein, the base shoulder engages the case shoulder to secure the attachment base to the case with the base optical opening optically aligned with the case optical opening.
 5. The attachment according to claim 1, wherein the at least one optical device of the attachment body includes a light detector and at least one attachment light source; and wherein a processor is configured to control operation of the at least one attachment light source based upon the light detector receiving optical signals from the mobile-device light source.
 6. The attachment of claim 5, wherein the attachment body includes a base plate with at least one communication opening; and wherein the light detector is disposed to receive the optical signals from the mobile-device light source via the at least one communication opening, when the attachment body is removably secured to the attachment base, the attachment base is secured to the case, and the case is secured to the mobile device.
 7. The attachment of claim 6, wherein the at least one optical device of the attachment body further includes an optical arrangement configured to direct light from the at least one attachment light source onto an external target during image targeting.
 8. The attachment of claim 7, wherein the attachment body includes an imaging opening, through which the imaging device acquires images of the external target; and wherein, the optical arrangement is configured to direct light onto the external target via the imaging opening.
 9. The attachment of claim 5, wherein the at least one attachment light source is configured to direct light onto an external target during image targeting and to direct light onto the imaging device to communicate with the mobile device.
 10. The attachment of claim 9, wherein the processor is configured to: control operation of the at least one attachment light source, based upon the light detector receiving optical signals from the mobile-device light source, to direct light onto the external target; and control operation of the at least one attachment light source to communicate with the mobile device via the imaging device.
 11. A system for communicating with a mobile device, the mobile device including an imaging device and a mobile-device light source, the system comprising: an attachment that includes: a light detector configured to receive optical signals from the mobile-device light source; and at least one attachment light source; and a processor configured to: based upon the optical signals received at the light detector from mobile-device light source, at least one of: activate the at least one attachment light source to direct light onto an external target; and configure at least one illumination parameter for the attachment; and activate the at least one attachment light source to communicate with the mobile device via the imaging device.
 12. The system of claim 11, with the imaging device arranged to acquire images of an external target, wherein the at least one attachment light source communicates with the mobile device by directing a series of flashes onto the external target to convey binary data via the acquired images.
 13. The system of claim 11, wherein the at least one attachment light source communicates with the mobile device by directing a series of flashes directly to the imaging device.
 14. The system of claim 11, wherein the at least one attachment light source includes: a first light source arranged to direct light, for image targeting, onto an external target; and a second light source arranged to direct light, for communication with the mobile device, to the imaging device.
 15. The system of claim 14, wherein the first light source is arranged to direct light onto the external target via an imaging opening; and wherein the second light source is arranged to direct light onto the imaging device via a communication opening that is distinct from the imaging opening.
 16. The system of claim 11, wherein the at least one attachment light source is activated to communicate one or more of an identification for the attachment, firmware information for the attachment, and battery status information for the attachment.
 17. The system of claim 11, wherein the optical signals received at the light detector from the mobile-device light source provide a firmware update for the attachment; and wherein the processor is further configured to implement the firmware update based upon the optical signals.
 18. A method of communicating information between a mobile device and an attachment, the mobile device including an imaging device and a mobile-device light source, and the attachment including a light detector and at least one attachment light source, the method comprising: receiving first optical signals at the light detector and, based on the first optical signals, at least one of: activating the at least one attachment light source for image acquisition and targeting; and configuring at least one illumination parameter for the attachment; and activating the at least one attachment light source to provide second optical signals to the imaging device to transmit non-image information to the mobile device.
 19. The method of claim 18, wherein the at least one attachment light source includes a first attachment light source and a second attachment light source; wherein the first attachment light source is activated for the image acquisition and targeting; and wherein the second attachment light source is activated to provide the second optical signals.
 20. The method of claim 18, wherein the non-image information is transmitted to the mobile device by: activating the at least one attachment light source to illuminate an external target; and imaging the external target with the imaging device.
 21. The method of claim 18, wherein the non-image information includes one or more of an identification for the attachment, firmware information for the attachment, and battery status information for the attachment.
 22. The method of claim 18, wherein the first optical signals received at the light detector encode a firmware update for the attachment; and wherein the method further comprises implementing the firmware update for the attachment based upon receiving the first optical signals. 